search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.33k stars 1.44k forks source link

Introduce v1alpha2 kube-proxy component config version #784

Open luxas opened 5 years ago

luxas commented 5 years ago

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

sttts commented 5 years ago

We need a thorough API review of the kube-proxy component config in the light of unifying them for all components. Moving what we have to beta in the 1.14 time frame feels like rushing in the light of us having just started with component-base.

claurence commented 5 years ago

@luxas I don't see a KEP for this issue links in the description. I'm removing it from the 1.14 milestone - to have it added back please file an exception request.

rosti commented 5 years ago

I am giving this a try. /assign

kacole2 commented 5 years ago

@luxas @rosti I'm the enhancement lead for 1.15. I don't see a KEP filed for this enhancement and per the guidelines, all enhancements will require one. Please let me know if this issue will have any work involved for this release cycle and update the original post reflect it. Thanks!

rosti commented 5 years ago

@kacole2 I am a bit skeptical for a KEP in this release cycle, however if we manage to put something before enhancements freeze for 1.15 then we'll ping you.

rosti commented 5 years ago

Initial proposal doc. This is shared with WG Component Standard, SIG Network, SIG Windows, SIG API Machinery and SIG Cluster Lifecycle. If someone has trouble accessing it, ping me.

mtaufen commented 5 years ago

@rosti thanks for picking this up! The common vs. local and per-platform config problems have needed someone who can really focus on them for a while, and I haven't been able to dedicate enough time lately. So I'm grateful someone's looking at this :). This is critical to the future of the componentconfig effort.

mtaufen commented 5 years ago

I left some comments on your doc.

mtaufen commented 5 years ago

@vllry, I heard you're also going to be working on kube-proxy componentconfig, wanted to make sure you see this.

stealthybox commented 5 years ago

@rosti, shall we tag this /w 1.16 and update KEP #1104?

alejandrox1 commented 5 years ago

Moving this to the 1.16 milestone to tackle during the next release /milestone v1.16

neolit123 commented 5 years ago

IMO we should have k/enhancements issues that track full graduation of APIs. from alpha->GA instead of separate ones for beta or GA.

rosti commented 5 years ago

If the KEP merges we can have an alpha version released before the end of the cycle, so I think, that it's appropriate to have it in 1.16.

mrbobbytables commented 4 years ago

Hey there @luxas, I'm one of the 1.16 Enhancement Shadows. Looks like you're on track for v1.16 :)

As a general reminder, the KEP must be merged and in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

kacole2 commented 4 years ago

Hi @luxas this is a reminder that the KEP needs to be merged by EOD tomorrow or it will be removed from the 1.16 milestone. Thanks.

kacole2 commented 4 years ago

@luxas @rosti

Enhancement Freeze has passed for 1.16. The KEP at #1104 was never merged and now this is being removed from the 1.16 milestone. If this would like to be re-added, please file an exception and it will require approval from the release lead.

/milestone clear

annajung commented 4 years ago

Hello @luxas @rosti, 1.17 Enhancement Shadow here! 🙂

I wanted to reach out to see if this enhancement will be graduating to alpha/beta/stable in 1.17?

 Please let me know so that this enhancement can be added to 1.17 tracking sheet.

Thank you!

🔔Friendly Reminder

rosti commented 4 years ago

Hi @annajung, The KEP PR is merged, it's in an implementable state and probably the first code PRs will start flowing in either next week or the week after that. So I think, that for now we are on a good track here.

annajung commented 4 years ago

Hey @rosti , Thanks for the update! I will add this enhancement to the tracking sheet to be tracked 👍

/milestone v1.17 /stage beta /tracked yes

annajung commented 4 years ago

Hey @rosti , Could you please post links to the tests in testgrid and keep track of any tests added for this enhancement?

Thank you!

pgburt commented 4 years ago

Hello @rosti, I'm one of the v1.17 docs shadows. Does this enhancement (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I'll do so).

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

pgburt commented 4 years ago

Hello @luxas @rosti. I see the docs for this enhancement is set to "Unknown" in the Enhancement Tracker sheet. Do we need to do any work to determine if this requires a placeholder PR for docs?

As a reminder, we're hoping to have placeholder PRs against kubernetes/website (branch dev-1.17) by Friday, Nov 8th. Thanks,

annajung commented 4 years ago

Hey @rosti 1.17 Enhancement Shadow here! 👋 I am reaching out to check in with you to see how this enhancement is going.

The Enhancement team needs to keep track of k/k PRs related to this enhancement in the tracking sheet. Could you please list out the k/k PRs that are in flight for this so we can track them?

Also, another friendly reminder that we're quickly approaching code freeze (Nov. 14th).

rosti commented 4 years ago

Hi @annajung and @pgburt, unfortunately this feature won't make it in time for 1.17. No PRs have been merged or are targeted for a merge before CF, so I would bet, that you want to untrack it for this release.

annajung commented 4 years ago

Thank you for the update @rosti. The Enhacement team have moved this from the tracking sheet

/milestone clear /tracked no

palnabarun commented 4 years ago

Hey there @rosti -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.18?

The current release schedule is:

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements

Thanks! :)

palnabarun commented 4 years ago

@rosti Just a friendly reminder, we are just 7 days away from the Enhancement Freeze (Tuesday, January 28th).

palnabarun commented 4 years ago

@rosti Just a friendly reminder, we are just 2 days away from the Enhancement Freeze (3 PM Pacific Time, Tuesday, January 28th).

rosti commented 4 years ago

@palnabarun sorry for the late response. This won't be making it in 1.18. Hence you can safely untrack it.

palnabarun commented 4 years ago

@rosti Thank you for the updates. I will update the tracking sheet accordingly.

fejta-bot commented 4 years ago

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

palnabarun commented 4 years ago

/remove-lifecycle stale

johnbelamaric commented 4 years ago

@rosti Enhancements shadow for 1.19 here. Anything planned for 1.19 for this?

johnbelamaric commented 4 years ago

Hi @rosti - Ping! Any plans for this in 1.19? We need to track it in the release team if so - please let me know.

Enhancements freeze is in one week, on May 19.

Note that recently the KEP format has changed. Additionally, #1620 merged recently, adding production readiness review questions to the KEP template. Please take this opportunity to reformat your KEP and also answer the questions add to the template in that PR.

Thanks!

rosti commented 4 years ago

Sorry for the delay @johnbelamaric ! I won't be doing any work here in 1.19 as it needs a KEP update and #1439 to land too.

johnbelamaric commented 4 years ago

Thanks @rosti.

fejta-bot commented 3 years ago

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

palnabarun commented 3 years ago

/remove-lifecycle stale

kikisdeliveryservice commented 3 years ago

Hi @rosti

Enhancements Lead here. Are there any plans for this 1.20?

Thanks! Kirsten

kikisdeliveryservice commented 3 years ago

Hi @rosti

Checking in again as Enhancements Freeze is next week Tuesday October 6th. Any plans for this?

As a note, the format of KEPs has changed. If you could please update and include the missing sections noted above that would be great. See for ref https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template

Thanks Kirsten

fejta-bot commented 3 years ago

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

fejta-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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 rotten

neolit123 commented 3 years ago

/remove-lifecycle rotten hoping that sig-network can pick the graduation of this config eventually.

jayunit100 commented 3 years ago

hiya folks, is anyone workin on this?

rikatz commented 3 years ago

/assign @jayunit100 @rikatz

OK, let's keep this on our track Jay. At least we know where it is, and how we can help on this.

But first we need to solve the flags/config conflicts (as Lubomir pointed in your original track) and then maybe propose to promote this :D

rikatz commented 3 years ago

@LappleApple marking you here just to be aware :D

jayunit100 commented 2 years ago

hi folks, anyone looking at this ?

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale