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.

Sign up for GitHub

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

Make the kube-proxy ComponentConfig v1beta1 #967

Closed
1 of 2 tasks
neolit123 opened this issue Jul 4, 2018 · 5 comments
Closed
1 of 2 tasks

Make the kube-proxy ComponentConfig v1beta1 #967

neolit123 opened this issue Jul 4, 2018 · 5 comments
Assignees
@luxas
Labels
area/ecosystem help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/refactor lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Next

Comments

@neolit123
Copy link
Member

neolit123 commented Jul 4, 2018 •
edited by timothysc
Loading

1.12 planning doc:
https://docs.google.com/document/d/1YP8sCtgo58yqQ9sR4nsn9iuVFmglCCBMivCTwjd1ERE/edit#

  • @timothysc to sync with mtaufen

  • Propagate hostname-override to kube-proxy
    Assigned: ?
    PR: ?
@neolit123 neolit123 added area/ecosystem priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/refactor labels Jul 4, 2018
@neolit123 neolit123 added this to the v1.12 milestone Jul 4, 2018
@neolit123 neolit123 added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jul 4, 2018
@chuckha chuckha modified the milestones: v1.12, GA Aug 15, 2018
@neolit123 neolit123 mentioned this issue Aug 17, 2018
Closed
28 tasks
@timothysc timothysc assigned luxas and unassigned timothysc Aug 26, 2018
@timothysc timothysc added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Aug 26, 2018
@timothysc
Copy link
Member

/assign @timothysc

@timothysc timothysc modified the milestones: GA, v1.13 Oct 26, 2018
@timothysc timothysc assigned timothysc and unassigned timothysc Oct 31, 2018
@timothysc timothysc removed this from the v1.13 milestone Oct 31, 2018
@timothysc timothysc removed their assignment Jan 5, 2019
@timothysc timothysc added this to the Next milestone Jan 5, 2019
@timothysc
Copy link
Member

@luxas are you going to be able to tackle this in 1.14?

@luxas
Copy link
Member

luxas commented Jan 6, 2019

@timothysc I hope so, but it depends on SIG Network approvers. After f2f discussions at KubeCon I'm optimistic about this happening in the next cycle though :)

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 6, 2019
@timothysc
Copy link
Member

Closing this should no longer apply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@luxas luxas

Labels
area/ecosystem help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/refactor lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
Next
Development

No branches or pull requests
6 participants
@chuckha @timothysc @neolit123 @luxas @k8s-ci-robot @fejta-bot