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
ApplySet : kubectl apply --prune
redesign and graduation strategy
#3659
Comments
/assign @KnVerey |
Hello @KnVerey Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this enhancement, it looks like #3661 will address most of these requirements.
The status of this enhancement is marked as |
This enhancement meets now meets all of the requirements to be tracked in v1.27. |
kubectl apply --prune
redesign and graduation strategykubectl apply --prune
redesign and graduation strategy
Docs placeholder PR: kubernetes/website#39818 |
Hi @KnVerey 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:
Please let me know if there are any PRs in k/k I should be tracking for this KEP. As always, we are here to help should questions come up. Thanks! |
Hi @KnVerey, 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! |
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 |
Hi @marosset they did make the release actually! You can see them here: https://github.com/orgs/kubernetes/projects/128/views/2. I will update the issue description. The only feature we were originally targeting as part of the first alpha that did not make it was |
/milestonve v1.27 |
@KnVerey I added this issue back into v1.27. |
BTW, nearly all the labels we register are using subdomains of If you want to make life easier for end users, get an exception in to change the labels, before beta (ideally, before the alpha release). I know it's a bit later, but it looks like we missed that detail in earlier reviews. See https://kubernetes.io/docs/reference/labels-annotations-taints/ for the list of registered keys that we use for labels and annotations. |
Enhancement Description
kubectl apply
's pruning feature, which enables cleanup of previously applied objects that have been removed from desired state provided to the currentapply
.k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
/sig cli
The text was updated successfully, but these errors were encountered: