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.

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

kubectl: Use Server-Side-Apply by default #3805

Open
8 tasks
alexzielenski opened this issue Jan 31, 2023 · 17 comments
Open
8 tasks

kubectl: Use Server-Side-Apply by default #3805

alexzielenski opened this issue Jan 31, 2023 · 17 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status

Comments

@alexzielenski
Copy link
Contributor

alexzielenski commented Jan 31, 2023

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 31, 2023
@alexzielenski
Copy link
Contributor Author

/sig cli

@k8s-ci-robot k8s-ci-robot added sig/cli Categorizes an issue or PR as relevant to SIG CLI. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 31, 2023
@KnVerey
Copy link
Contributor

KnVerey commented Feb 2, 2023

/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

@k8s-ci-robot k8s-ci-robot added the stage/beta Denotes an issue tracking an enhancement targeted for Beta status label Feb 2, 2023
@KnVerey
Copy link
Contributor

KnVerey commented Feb 2, 2023

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

@k8s-ci-robot k8s-ci-robot added this to the v1.27 milestone Feb 2, 2023
@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Feb 2, 2023
@marosset
Copy link
Contributor

marosset commented Feb 3, 2023

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!

@KnVerey
Copy link
Contributor

KnVerey commented Feb 8, 2023

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

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Feb 8, 2023
@KnVerey
Copy link
Contributor

KnVerey commented Feb 9, 2023

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

@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Feb 9, 2023
@soltysh
Copy link
Contributor

soltysh commented Feb 9, 2023

/stage alpha

@k8s-ci-robot k8s-ci-robot added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels Feb 9, 2023
@shatoboar
Copy link

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.

@marosset
Copy link
Contributor

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

@marosset
Copy link
Contributor

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

@marosset marosset added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Feb 10, 2023
@apelisse
Copy link
Member

I'll update asap

@apelisse
Copy link
Member

#3873

@Rishit-dagli
Copy link
Member

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!

@shatoboar
Copy link

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!

@marosset
Copy link
Contributor

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

@k8s-ci-robot k8s-ci-robot added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Mar 15, 2023
@k8s-ci-robot k8s-ci-robot removed this from the v1.27 milestone Mar 15, 2023
@k8s-ci-robot k8s-ci-robot removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Mar 15, 2023
@Atharva-Shinde Atharva-Shinde removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels May 14, 2023
@k8s-triage-robot
Copy link

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

@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 Jan 20, 2024
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
Status: Removed From Milestone
Status: Needs Triage
Status: Backlog Improving CI/CD SSA
Development

No branches or pull requests

10 participants