This repository has been archived by the owner on Aug 4, 2023. It is now read-only.
fix: set containerPort to targetPort if defined #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
containerPort
gets set to the templateport
, andtargetPort
is ignored even when defined. This causes an issue whereport
actually points to the external ClusterIP port, and thetargetPort
is the port where the service is exposed from the container. Hence, in the case wheretargetPort
is defined,containerPort
should be set totargetPort
and not the external ClusterIP port.eg: defining ports in kubekutr config like:
sets the containerPort to
9000
instead of8000
, which is wrong in this case because9000
is the port which is exposed to the cluster, and8000
is the port that the container is supposed to expose.