-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
declare ipvs proxier beta #6524
Conversation
ipvs alpha version -> beta version
/priority critical-urgent |
Deploy preview ready! Built with commit 0c01661 https://deploy-preview-6524--kubernetes-io-master-staging.netlify.com |
@a-mccarthy @steveperry-53 @jaredbhatti It's very import to IPVS proxier beta work, please take a look when you have a chance. Thanks! |
We want to declare IPVS proxier beta in v1.9, see kubernetes/enhancements#265 This PR is also the required document in https://docs.google.com/spreadsheets/d/1WmMJmqLvfIP8ERqgLtkKuE_Q2sVxX8ZrEcNxlVIJnNc/ for 'Implement IPVS-based in-cluster service load balancing' feature. |
/cc @thockin |
adding do-not-merge because kubernetes/kubernetes#56623 is still not in. Docs should be updated only when the implementation is in place. removing critical-urgent because ... cannot feel the urgency |
implementation is already in place!
kubernetes/kubernetes#56623 just declares beta. |
@m1093782566 it is not yet officially announced as beta, so please hold doc changes. |
kubernetes/kubernetes#56623 is in now... this one is good to go. |
Does need commit another PR to |
@stewart-yu Yes. A commit to release-1.9 is needed. Look, the process of merging documentation is a little bit different from that for a code repo. If a doc PR is targeting Master and it is merged, the content is published on k8s.io/docs immediately. Commiting to release-1.9 will help ensure that v1.9 specific contents are only online when it is officially released. |
Closing this for merging #6558 into release-1.9. |
ipvs alpha version -> beta version
cc @m1093782566
This change is