-
Notifications
You must be signed in to change notification settings - Fork 153
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
Support for configuring IPFamilies and IPFamilyPolicy for nodeport-proxy #12472
Conversation
Signed-off-by: Waleed Malik <ahmedwaleedmalik@gmail.com>
@@ -574,6 +574,10 @@ spec: | |||
requests: | |||
cpu: 50m | |||
memory: 32Mi | |||
# IPFamilies configures the IP families to use for the LoadBalancer service. | |||
ipFamilies: null |
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.
Not sure if we should leave this as is for demonstration purposes or redact this field from the example. WDYT @xrstf? I would like to avoid defaulting it to let's say IPv4
or something since it's mostly determined by the configuration that you used to create the underlying kubernetes cluster.
/approve |
LGTM label has been added. Git tree hash: 5174793f53e6ea044d21f00d81489176bcd316ed
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, xrstf The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
/cherry-pick release/v2.23 |
@ahmedwaleedmalik: new pull request created: #12480 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What this PR does / why we need it:
This PR adds support for configuring IPfamilies and IPFamilyPolicy for nodeport-proxy. This is essential for cases where we need either both IPv4 and IPv6 addresses, just IPv6 IP, IPv6 IP for the LoadBalancer, etc.
Which issue(s) this PR fixes:
Fixes #12471
What type of PR is this?
/kind feature
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: