-
Notifications
You must be signed in to change notification settings - Fork 107
Make extension ports configurable via helm values #1229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make extension ports configurable via helm values #1229
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Any opinion regarding adding an assertion on the deployment chart for the number of ports to be provided ?
/hold |
c49fe3e
a8cd155
to
c49fe3e
Compare
/unhold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
How to categorize this PR?
/area networking
/kind enhancement
/platform aws
What this PR does / why we need it:
Make extension ports configurable via helm values.
In certain scenarios, e.g. in the autonomous cluster use case, multiple extensions may run side-by-side in the host network. In this case, they cannot use the same ports. Therefore, it should be possible to inject the usable ports from outside via helm values.
Which issue(s) this PR fixes:
Part of gardener/gardener#2906
Special notes for your reviewer:
Release note: