Support routing directly to pods #449
Merged
Conversation
This file contains 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
k8s-ci-robot
added
size/L
…n set to `pod` will configure the Target Group to use the pod ip and port for the targets.
…sage of the default rule's target group for the listeners default action. it should be using the default backend service
|
This PR also solves a aws-vpc-cni issue |
k8s-ci-robot
added
size/XL
|
We would definitely use this |
This change removes the extra backticks from the first deploy step in the walkthrough.md.
bigkraig
added a commit
that referenced
this pull request
Oct 1, 2018
Support routing directly to pods
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.
Resolves #343, this annotation will configure the target group to route directly to the service endpoint
pod ip:port.