Allow specifying externalIPs for ingress-nginx #164
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
kvaps
force-pushed
the
externalips-ingress
branch
from
33a000d to
78ce6c5
Compare
kvaps
force-pushed
the
externalips-ingress
branch
from
78ce6c5 to
10bbcde
Compare
This was referenced Jun 17, 2024
Merged
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.
There is a configuration without load-balancer service, when all nodes of the cluster are responsible for routing traffic.
In this case we can provide user an oportunity to specify IP-addresses of the nodes which are used to recieve traffic.
These nodes will be used to route traffic to nginx-ingress pods.
fixes #158