Enhancements: Implement IPVS-based in-cluster service load balancing

Created on 24 Apr 2017  路  33Comments  路  Source: kubernetes/enhancements

Feature Description

  • One-line feature description (can be used as a release note): Implement IPVS-based in-cluster service load balancing
  • Primary contact (assignee): @m1093782566 (@quinton-hoole acting as proxy as @haibinxie is not yet a member of the K8s org)
  • Responsible SIGs: sig-networking
  • Design proposal link (community repo): See https://github.com/kubernetes/kubernetes/issues/44063
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @thockin @quinton-hoole
  • Approver (likely from SIG/area to which feature belongs): @thockin
  • Initial target stage (alpha/beta/stable) and release (x.y):

    • alpha in v1.8

    • beta in v1.9

    • GA in v1.10

cc: @kubernetes/sig-network-feature-requests

kinfeature sinetwork stagstable

Most helpful comment

Closing this as the feature is GA in 1.11. Please feel free to reopen if there is still a need to track this.
/close

All 33 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

kubernetes/community#692

@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?

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:

kubernetes/kubernetes#52014, kubernetes/kubernetes#52330

@m1093782566 Can you please link to the user-facing documentation (kubernetes.io/docs) for this feature?

@luxas

Sure. I think @Lion-Wei is already working on it. Could you please provide the link, @Lion-Wei?

Would be really good to get some docs. @m1093782566

@apsinha

Please check the design proposal: kubernetes/community#692 and user documents: https://github.com/kubernetes/kubernetes.github.io/pull/5571

merged as alpha in 1.8

Reopening this to target beta in v1.9: https://github.com/kubernetes/features/issues/494

Looking to move this out of alpha and into beta for v1.9.

Tracking the work that needs to be done here: https://github.com/kubernetes/kubernetes/issues/51602

@quinton-hoole :wave: Please indicate in the 1.9 feature tracking board
whether this feature needs documentation. If yes, please open a PR and add a link to the tracking spreadsheet. Thanks in advance!

@quinton-hoole Bump for docs 鈽濓笍

/cc @idvoretskyi

@zacharysarah

please check https://github.com/kubernetes/website/pull/6425/files#diff-5701136fd2ce258047b6ddc389112352R701 and https://github.com/kubernetes/kubernetes/tree/master/pkg/proxy/ipvs

If they are still not enough, @stewart-yu will do help. Thanks!

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 https://github.com/kubernetes/kubernetes/pull/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
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

  • Description
  • Milestone
  • Assignee(s)
  • Labels:

    • stage/{alpha,beta,stable}

    • sig/*

    • kind/feature

cc @idvoretskyi

@cmluciano @m1093782566 @Lion-Wei @quinton-hoole @kubernetes/sig-network-feature-requests --
We noticed that there was no response on this feature for the 1.11 Release Cycle, yet it's on the 1.11 Features tracking spreadsheet.

At this point, an exception would need to be filed for this to make it into the 1.11 milestone.
Please follow the process detailed here.

In addition, please update the line item for this feature on the Milestone risks sheet ASAP AND ping myself and @idvoretskyi, so we can assess the feature status or we will need to officially remove it from the milestone.

Exception was approved by @jberkus.
Just noting for record. This has been moved back to the primary sheet.

Closing this as the feature is GA in 1.11. Please feel free to reopen if there is still a need to track this.
/close

Was this page helpful?
0 / 5 - 0 ratings