-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
ServiceIPStaticSubrange alpha feature in 1.24 #32344
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @nate-double-u @thockin |
✔️ Deploy Preview for kubernetes-io-main-staging ready! 🔨 Explore the source changes: 2726b74 🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/62343e688b2a1c0008842690 😎 Browse the preview: https://deploy-preview-32344--kubernetes-io-main-staging.netlify.app |
@@ -201,6 +201,7 @@ different Kubernetes components. | |||
| `ServiceLBNodePortControl` | `true` | Beta | 1.22 | | | |||
| `ServiceLoadBalancerClass` | `false` | Alpha | 1.21 | 1.21 | | |||
| `ServiceLoadBalancerClass` | `true` | Beta | 1.22 | | | |||
| `ServiceIPStaticSubrange` | `false` | Alpha | 1.24 | | |
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.
This line should go before line 198.
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.
haha, yeah
@@ -1032,6 +1033,9 @@ Each feature gate is designed for enabling/disabling a specific feature: | |||
topology of the cluster. See | |||
[ServiceTopology](/docs/concepts/services-networking/service-topology/) | |||
for more details. | |||
- `ServiceIPStaticSubrange`: Enable a new strategy for Services ClusterIP allocations, so users can subdivide the ClusterIP range. Dynamic allocated ClusterIP addresses will be allocated preferently from the upper range allowing users to assign static ClusterIPs from the lower range with a low risk of collision. See |
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.
Please wrap the long line as we did for other entries.
- `ServiceIPStaticSubrange`: Enable a new strategy for Services ClusterIP allocations, so users can subdivide the ClusterIP range. Dynamic allocated ClusterIP addresses will be allocated preferently from the upper range allowing users to assign static ClusterIPs from the lower range with a low risk of collision. See | |
- `ServiceIPStaticSubrange`: Enable a new strategy for Services ClusterIP allocations, | |
so users can subdivide the ClusterIP range. Dynamic allocated ClusterIP addresses | |
will be allocated preferently from the upper range allowing users to assign static ClusterIPs | |
from the lower range with a low risk of collision. See |
This should target at the |
let me reopen a new one on that branch Thanks |
You can change the target branch without opening a new PR, you can use the GitHub web UI to change it. (That way you don't lose the history of the PR) |
/sig network
KEP kubernetes/enhancements#3070