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.

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

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/784#issuecomment-1132018602): >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: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
k8s-triage-robot commented 12 months ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 12 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/enhancements/issues/784#issuecomment-1636493924): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
thockin commented 10 months ago

We really do need to fix the k-p config vs flags mess.

pohly commented 10 months ago

See also https://github.com/kubernetes/kubernetes/issues/119864 regarding how adding config options for logging broke logging command flags. This was fixed just in time before the 1.28 release.

sftim commented 10 months ago

:thought_balloon: how come this enhancement doesn't aim to graduate that config to stable?

k8s-triage-robot commented 5 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

danwinship commented 5 months ago

/remove-lifecycle stale /label lead-opted-in

k8s-ci-robot commented 5 months ago

@danwinship: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads]

In response to [this](https://github.com/kubernetes/enhancements/issues/784#issuecomment-1924741398): >/remove-lifecycle stale >/label lead-opted-in Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
danwinship commented 5 months ago

@danwinship: Can not set label lead-opted-in: Must be member in one of these teams: [... sig-network-leads ...]

um?

thockin commented 5 months ago

I think it means https://github.com/orgs/kubernetes/teams/sig-network-leads which is https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-network/teams.yaml

aroradaman commented 5 months ago

/retitle Graduate the kube-proxy ComponentConfig to v1alpha2

aroradaman commented 5 months ago

Link to PR with the updated proposal, design, and PRR questionnaire of KEP: https://github.com/kubernetes/enhancements/pull/4337

aroradaman commented 5 months ago

/retitle Introduce v1alpha2 kube-proxy component config version

pnbrown commented 5 months ago

Hello @jayunit100 @rikatz 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage alpha for v1.30 (correct me, if otherwise)

Here’s where this enhancement currently stands:

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

neolit123 commented 5 months ago

@pnbrown hello, not sure what is in the release team role book on this one, but it's better to ping the "assigned" folks and not the author of the ticket.

pnbrown commented 5 months ago

@neolit123 my apologies. I'll fix.

aroradaman commented 5 months ago

/assign

chanieljdan commented 4 months ago

Hi @jayunit100 @rikatz 👋, 1.30 Docs Shadow here.

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

a-mccarthy commented 4 months ago

Hi @jayunit100 and @rikatz,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository. The placeholder PR deadline is 27th February, 2024. Here's the 1.30 Release Calendar

chanieljdan commented 4 months ago

Hi @jayunit100 @rikatz 👋, 1.30 Docs Shadow here.

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

Hi @jayunit100 @rikatz @aroradaman 👋, just want to follow up on this, if you could review, thanks!

rikatz commented 4 months ago

Hi, tbh I have no idea on the status of this feature

aroradaman commented 4 months ago

Hi @jayunit100 @rikatz @aroradaman 👋, just want to follow up on this, if you could review, thanks!

@chanieljdan I have created the placeholder PR.

pnbrown commented 4 months ago

Hey again @jayunit100 @rikatz @aroradaman 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

Here's where this enhancement currently stands:

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!

danwinship commented 4 months ago

/unassign @jayunit100 @rikatz to avoid confusion since they're not currently working on this

salehsedghpour commented 4 months ago

Hello @aroradaman 👋 Enhancements team here,

Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.30 milestone.

If you still wish to progress this enhancement in v1.30, please file an exception request. Thanks!

/milestone clear

thockin commented 2 months ago

Hi @aroradaman, are you aiming for 1.31 now?

aroradaman commented 2 months ago

Yes!

thockin commented 2 months ago

We should figure out how we want to manage this KEP. As stated the KEP's goal is an alpha. That's unusual. Perhaps we should update the KEP to make the goal a GA config API, and then track the lifecycle as such?

sreeram-venkitesh commented 1 month ago

@aroradaman Since you're aiming for 1.31 and the KEP already has a lead-opted-in label its been added to the 1.31 enhancements tracking board. Please let me know if this works!

sreeram-venkitesh commented 1 month ago

@aroradaman, since this KEP is still targeting alpha in v1.31, can we update the label to stage/alpha and remove the existing stage/beta?

ArkaSaha30 commented 1 month ago

Hello @aroradaman 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting for stage alpha for v1.31 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, we would just need to update the following:

Other than the above-mentioned AIs, all the KEP requirements are in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

sreeram-venkitesh commented 1 month ago

/stage alpha

Princesso commented 3 weeks ago

Hello @aroradaman :wave:, 1.31 Docs Lead here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follow the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you!

sreeram-venkitesh commented 3 weeks ago

Hello 👋, v1.31 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze. This KEP still doesn't have an updated kep.yaml with the latest-milestone and the alpha milestone updated to v1.31,

If you still wish to progress this enhancement in v1.31, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

sreeram-venkitesh commented 3 weeks ago

/milestone clear

sreeram-venkitesh commented 2 weeks ago

Marking the KEP as tracked for enhancements freeze since the exception request was approved and with #4732 merged.

mbianchidev commented 2 weeks ago

Hey @luxas

:wave: from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

Princesso commented 1 week ago

Hello @aroradaman 👋, 1.31 Docs Lead here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follow the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you!

hi @aroradaman, gentle reminder to open a draft PR for this enhancement before Thursday June 27, 2024.

mbianchidev commented 1 week ago

Hey @luxas

👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

Reminder of the 3rd of July deadline! It's totally fine to also opt out if you don't think that writing a blog is useful for our users or if you don't have time (in that case team comms can also help you out :eyes: )

ArkaSaha30 commented 4 hours ago

Hey again @aroradaman 👋, Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

Here's where this enhancement currently stands:

Regarding this enhancement, it appears that there is currently one PR (https://github.com/kubernetes/kubernetes/pull/121830) in k/k repository.

For this KEP, we would need to do the following:

If you anticipate missing code freeze, you can file an exception request in advance.

The status of this enhancement is marked as at risk for code freeze.