-
Notifications
You must be signed in to change notification settings - Fork 1.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
Implement IPVS-based in-cluster service load balancing #265
Comments
Is this a dupe / replacement of #196? |
As discussed in SIG-Network meeting, the proposal has not been finalized according to the issues linked in the description. These issues should be addressed prior to an official milestone assignment. |
I raised a PR about design proposa of supporting ipvs mode for kube-proxy, please check |
@quinton-hoole @kubernetes/sig-network-feature-requests any updates for 1.8? Is this feature still on track for the release? |
@quinton-hoole @kubernetes/sig-network-feature-requests can you confirm that this feature targets 1.8? If yes, please, update the features tracking spreadsheet with the feature data, otherwise, let's remove this item from 1.8 milestone. Thanks |
@idvoretskyi yes it's on track for 1.8 after lots of efforts. I see it's already in the spreedsheet item 22. could you double check if it's good? |
@haibinxie sorry, it's there. Thanks! |
@haibinxie both the document and this issue don't link to any PRs. Can you link here so one can take a look? |
Please check PR kubernetes/kubernetes#46580 and design proposal kubernetes/community#692 FYI |
thanks a lot! excited to try this out. |
Thanks, @pires Please note that it's still in alpha version and there are already some PRs about small bug fixes in fly, xref: |
@m1093782566 Can you please link to the user-facing documentation (kubernetes.io/docs) for this feature? |
Would be really good to get some docs. @m1093782566 |
Please check the design proposal: kubernetes/community#692 and user documents: kubernetes/website#5571 |
As we discussed in sig-netork meeting, we are targeting GA in 1.10. |
@quinton-hoole Would you please re-tag this issue to 1.10 and stage/stable? |
@m1093782566 updated. |
Thanks Kevin! |
@m1093782566 based on the conversation at kubernetes/kubernetes#56319, can you confirm that the feature is still on track for 1.10? |
we are targetting 1.11 now |
@m1093782566 please, updated the feature target stage and milestone. Thanks |
Moved milestone out of v1.10. |
@cmluciano @m1093782566 @kubernetes/sig-network-feature-requests If so, can you please ensure the feature is up-to-date with the appropriate:
cc @idvoretskyi |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Declare IPVS-based kube-proxy GA and remove feature gateway **What this PR does / why we need it**: As discussed in sig-network meeting, we decided to target IPVS-based kube-proxy GA in 1.10. This PR declares IPVS-based kube-proxy GA and remove feature gateway. **Which issue(s) this PR fixes**: Fixes: #58443 issue in feature repo: kubernetes/enhancements#265 **Special notes for your reviewer**: **Release note**: ```release-note Declare IPVS-based kube-proxy GA ``` @quinton-hoole
@cmluciano @m1093782566 @Lion-Wei @quinton-hoole @kubernetes/sig-network-feature-requests -- At this point, an exception would need to be filed for this to make it into the 1.11 milestone. In addition, please update the line item for this feature on the |
Exception was approved by @jberkus. |
Closing this as the feature is GA in 1.11. Please feel free to reopen if there is still a need to track this. |
Feature Description
cc: @kubernetes/sig-network-feature-requests
The text was updated successfully, but these errors were encountered: