search

kubernetes / enhancements

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

Separate kubectl user preferences from cluster configs #3104

Open eddiezane opened 2 years ago

eddiezane commented 2 years ago

Enhancement Description

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

soltysh commented 2 years ago

/milestone v1.25 /stage alpha

jasonbraganza commented 2 years ago

Hello @eddiezane 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

Looks like for this one, we would need to update the following in the open PR https://github.com/kubernetes/enhancements/pull/3392:

For note, the status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

jasonbraganza commented 2 years ago

Hello @eddiezane 👋🏿 Just checking in, as we are four days away from the enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT.

Please get the open PR https://github.com/kubernetes/enhancements/pull/3392 merged with the suggestions in the previous comment

Please note: the current status of the enhancement is at-risk. Thank you.

parul5sahoo commented 2 years ago

Hi @eddiezane 👋

Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure the following items are completed:

There seems to no open or close PR in k/k. However, correct me if I am wrong and enlist the open or merged PRs in the comments. So, that we can mark the enhancement as tracked.

As always, we are here to help should questions come up.

Thanks!!

cathchu commented 1 year ago

Hey @eddiezane :wave:

1.25 Release Docs Shadow here. Does this enhancement work planned for 1.25 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.25 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before August 4. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

parul5sahoo commented 1 year ago

Hi @eddiezane :wave:

Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022. Which is in two days

Please ensure the following items are completed:

Priyankasaggu11929 commented 1 year ago

Hello :wave:, 1.25 Enhancements Lead here.

Unfortunately, this enhancement did not meet the code freeze criteria because there are still unmerged k/k code PRs.

If you still wish to progress this enhancement in v1.25, please file an exception request. Thank you so much!

/milestone clear

k8s-triage-robot commented 1 year 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 1 year 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

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active 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 rotten

enj commented 1 year ago

/remove-lifecycle rotten

k8s-triage-robot commented 6 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

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough active 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 rotten

k8s-triage-robot commented 4 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 4 months ago

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

In response to [this](https://github.com/kubernetes/enhancements/issues/3104#issuecomment-2009067132): >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.
ardaguclu commented 3 months ago

/reopen

k8s-ci-robot commented 3 months ago

@ardaguclu: Reopened this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/3104#issuecomment-2026649708): >/reopen 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.
eddiezane commented 3 months ago

/unassign @eddiezane /assign @ardaguclu

eddiezane commented 3 months ago

/remove-lifecycle rotten

ardaguclu commented 1 month ago

@eddiezane could you please add lead-opt-in label to track the work?. Thanks.

eddiezane commented 1 month ago

/label lead-opted-in

soltysh commented 1 month ago

/milestone v1.31

sreeram-venkitesh commented 1 month ago

Hello @ardaguclu 👋, v1.31 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, since https://github.com/kubernetes/enhancements/pull/3392 was merged almost 2 years ago, we'd need to do the following:

The status of this enhancement is marked as At risk for enhancements freeze. Once the above tasks are done, I can mark it as tracked.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you!

soltysh commented 1 month ago

@sreeram-venkitesh updated KEP in https://github.com/kubernetes/enhancements/pull/4705

sreeram-venkitesh commented 1 month ago

@soltysh Thank you, marking the KEP as Tracked for enhancements freeze 🎉

Princesso commented 1 month ago

Hello @ardaguclu @eddiezane :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!

edithturn commented 1 month ago

Hello, @ardaguclu!

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

ardaguclu commented 1 month ago

@edithturn thank you for comment. I believe that we should definitely write a feature blog about kuberc. However, for this release kuberc will first be released as an alpha feature and hidden behind an environment variable. I think, it is better to write feature blog in next release after promoting it to beta. WDYT @eddiezane ?.

edithturn commented 3 weeks ago

Hello @ardaguclu , @eddiezane 👋!

I was wondering if you have decided to write a feature blog about kuberc for this release or for the next one.

This is just a friendly reminder: if you need to open a Feature Blog placeholder PR against the website repository, please go ahead and do so. If you have any questions or need any help, feel free to reach out! For more information about writing a blog, check out the blog contribution guidelines.

The deadline for this is July 03, 2024, at 18:00 PDT.

Thank you!! Edith

sreeram-venkitesh commented 2 weeks ago

Hey again @ardaguclu 👋 v1.31 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:

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):

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

I'm marking this KEP as At risk for code freeze for now since the PR isn't approved yet. But everything looks good so far and I can mark the KEP as tracked as soon as the code is approved. Thanks for keeping the issue description up to date! Also, please let me know if there are other PRs in k/k we should be tracking for this KEP (I couldn't find any after I did a search so looks like we only have a single PR). As always, we are here to help if any questions come up. Thanks!

sreeram-venkitesh commented 1 week ago

Hi again @ardaguclu! We are one week away from code freeze and I wanted to ping you here as a friendly reminder to get your code PRs merged in time before the deadline. Please let me know if I need to be tracking any PRs other than https://github.com/kubernetes/kubernetes/pull/125230 too. Thanks!

sreeram-venkitesh commented 17 hours ago

Hello @ardaguclu 👋 v1.31 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.31 milestone.

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!

/milestone clear