Skip to content
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

Jump to bottom

Implement IPVS-based in-cluster service load balancing #265

Closed
ghost opened this issue Apr 24, 2017 · 33 comments
Closed

Implement IPVS-based in-cluster service load balancing #265

ghost opened this issue Apr 24, 2017 · 33 comments
Assignees
@justaugustus @cmluciano @m1093782566
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/network Categorizes an issue or PR as relevant to SIG Network. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Milestone
v1.11

Comments

@ghost
Copy link

ghost commented Apr 24, 2017 •
edited by idvoretskyi

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 Implement IPVS-based in-cluster service load balancing kubernetes#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
@ghost ghost added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Apr 24, 2017
@ghost ghost added this to the v1.7 milestone Apr 24, 2017
@ghost ghost self-assigned this Apr 24, 2017
@smarterclayton
Copy link
Contributor

Is this a dupe / replacement of #196?

@idvoretskyi idvoretskyi added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label May 3, 2017
@idvoretskyi idvoretskyi added this to In Progress in Kubernetes 1.7 features May 3, 2017
@cmluciano cmluciano modified the milestones: next-milestone, v1.7 May 4, 2017
@cmluciano
Copy link

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.

@dhilipkumars dhilipkumars mentioned this issue Jun 7, 2017
Merged
@m1093782566
Copy link

I raised a PR about design proposa of supporting ipvs mode for kube-proxy, please check

kubernetes/community#692

@idvoretskyi idvoretskyi removed this from In Progress in Kubernetes 1.7 features Jun 8, 2017
@ghost ghost modified the milestones: 1.8, next-milestone Jul 13, 2017
@caseydavenport caseydavenport mentioned this issue Jul 13, 2017
Closed
23 tasks
@idvoretskyi idvoretskyi added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 25, 2017
@idvoretskyi
Copy link
Member

@quinton-hoole @kubernetes/sig-network-feature-requests any updates for 1.8? Is this feature still on track for the release?

@idvoretskyi
Copy link
Member

@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 idvoretskyi added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Sep 18, 2017
@haibinxie
Copy link

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

@idvoretskyi
Copy link
Member

@haibinxie sorry, it's there. Thanks!

@idvoretskyi idvoretskyi removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Sep 19, 2017
@pires
Copy link

pires commented Sep 20, 2017

@haibinxie both the document and this issue don't link to any PRs. Can you link here so one can take a look?

@m1093782566
Copy link

@pires

Please check PR kubernetes/kubernetes#46580 and design proposal kubernetes/community#692

FYI

@pires
Copy link

pires commented Sep 20, 2017

thanks a lot! excited to try this out.

@m1093782566
Copy link

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

@luxas
Copy link
Member

luxas commented Sep 21, 2017

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

@m1093782566
Copy link

m1093782566 commented Sep 21, 2017 •
edited

@luxas

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

@apsinha
Copy link

apsinha commented Sep 25, 2017

Would be really good to get some docs. @m1093782566

@m1093782566
Copy link

@apsinha

Please check the design proposal: kubernetes/community#692 and user documents: kubernetes/website#5571

@m1093782566
Copy link

As we discussed in sig-netork meeting, we are targeting GA in 1.10.

@m1093782566
Copy link

@quinton-hoole Would you please re-tag this issue to 1.10 and stage/stable?

@kevin-wangzefeng kevin-wangzefeng modified the milestones: v1.9, v1.10 Jan 18, 2018
@kevin-wangzefeng kevin-wangzefeng added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels Jan 18, 2018
@kevin-wangzefeng
Copy link
Member

@m1093782566 updated.

@m1093782566
Copy link

Thanks Kevin!

@m1093782566 m1093782566 mentioned this issue Jan 18, 2018
Merged
@idvoretskyi idvoretskyi added kind/feature Categorizes issue or PR as related to a new feature. tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Jan 29, 2018
@m1093782566 m1093782566 mentioned this issue Feb 6, 2018
Closed
@idvoretskyi
Copy link
Member

@m1093782566 based on the conversation at kubernetes/kubernetes#56319, can you confirm that the feature is still on track for 1.10?

@m1093782566
Copy link

we are targetting 1.11 now

@idvoretskyi
Copy link
Member

@m1093782566 please, updated the feature target stage and milestone.

Thanks

@feiskyer feiskyer modified the milestones: v1.10, next-milestone Feb 14, 2018
@feiskyer
Copy link
Member

Moved milestone out of v1.10.

@justaugustus
Copy link
Member

@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

k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this issue May 31, 2018
Merge pull request #58442 from m1093782566/ipvs-ga
f5254da 
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
@justaugustus
Copy link
Member

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

@justaugustus
Copy link
Member

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

@justaugustus justaugustus modified the milestones: next-milestone, v1.11 Jun 6, 2018
@justaugustus
Copy link
Member

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

@caseydavenport caseydavenport mentioned this issue Oct 11, 2018
Closed
@kacole2 kacole2 removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Oct 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justaugustus justaugustus

@cmluciano cmluciano

@m1093782566 m1093782566

Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/network Categorizes an issue or PR as relevant to SIG Network. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
None yet
Milestone
v1.11
Development

No branches or pull requests