/sig cli

/lead-opted-in

We're still finalizing what the process framing should look like given that this is about a GA feature but still requires a risk assessment, staged rollout plan, etc. Current thinking is we'll frame what already exists as alpha and the changes as betas->GA progression. So, tenatively:
/stage beta

/milestone v1.27
/label lead-opted-in

Hello @alexzielenski 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage beta for v1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this enhancement, it looks like #3831 will address the remaining requirements.

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!

/remove-label lead-opted-in
/remove-milestone 1.27

We've decided this requires more time for discussion than available ahead of enhancement freeze for this release.

Sorry for the back and forth. We discussed this KEP at both the SIG CLI and PRR meetings today, and although the plan towards SSA by default needs wide discussion and will not be ready in time for the freeze, we tentatively want to keep one small piece in the proposal for 1.27: the --server-side=auto feature, as an alpha behind an env var. So I'm opting the enhancement back in for that.

/label lead-opted-in

/stage alpha

Hi @alexzielenski,
A friendly reminder that are approaching the enhancement freeze in a couple hours at 18:00 PDT Thursday 9th February 2023 :)
It looks like https://github.com/kubernetes/enhancements/pull/3831/files isn't merged yet, and the status of this enhancement is still marked as at risk.

I just noticed that the kep.yaml for this enhancement still has status: provisional can someone make a PR to update this?
@soltysh @KnVerey @alexzielenski

We are now past the v1.27 code freeze and the only issue is the status in the kep.yaml still says this enhancement is provisional.
Since this is a minor issue I'm going to include this enhancement in v1.27 as tracked but please update the kep.yaml ASAP
@salaxander - FYI

I'll update asap

#3873

Hi @alexzielenski 👋, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.
Please feel free to reach out with any questions. Thanks!

Hi @alexzielenski 👋,
Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.
Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

Please let me know what PRs in k/k I should be tracking for this KEP.
As always, we are here to help should questions come up. Thanks!

Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release.

If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

/milestone clear
/remove-label tracked/yes
/label tracked/no

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

This bot triages un-triaged 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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

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:

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

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

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

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

/close not-planned

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