No need for Service type NodePort in Step 3 #1041
Open
+0
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There is no need to configure the Service type as NodePort. In Ingress manifest target type IP is used hence the traffic will be sent directly to the Pod IP. Hence NodePort is unnecessary. Service type ClusterIP is enough. This is a reoccurring misleading guidance which I requested to be corrected in AWS blogs as well.
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #, if available: None.
Description of changes: Removed type : NodePort in Step 3. There is no need to configure the Service type as NodePort. In Ingress manifest target type IP is used hence the traffic will be sent directly to the Pod IP. Hence NodePort is unnecessary. Service type ClusterIP is enough. This is a reoccurring misleading guidance which I requested to be corrected in AWS blogs as well.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.