-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Removing In-Tree Cloud Providers #2395
Comments
Migrating all the old template keps to new template : #2391 |
/assign |
/sig cloud-provider |
Hi @andrewsykim, even with PR #2443 merged, you are missing both test plans and graduation criteria. Could you make sure the requirements are added into the KEP before the freeze EOD PST? |
@annajung that KEP is really old and predates the new template, do you need that updated by EOD today? There are some other KEPs I need to get to and I don't think I'll have time to revisit this one. |
Hi @andrewsykim Enhancements Freeze is now in effect. Unfortunately, KEP for this enhancement does not meet all the required criteria. If you wish to be included in the 1.21 Release, please submit an Exception Request as soon as possible. /milestone clear |
Hi @andrewsykim Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:
As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them. Thanks! |
Hi @andrewsykim Enhancements team is marking this enhancement as "At Risk" for the upcoming code freeze due to not seeing any linked k/k PR(s) for this enhancement. Please make sure to provide all k/k PR(s) and k/website PR(s) to this issue so it can be tracked by the release team. |
Hey @andrewsykim A friendly reminder that Code freeze is 5 days away, March 9th EOD PST Any enhancements that are NOT code complete by the freeze will be removed from the milestone and will require an exception to be added back. Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST Thanks! |
Hi @andrewsykim, with code freeze now in effect, we are removing this enhancement from 1.21 release due to no code PR being tracked for this enhancement. If needed, feel free to file an exception to add this back into the release. thanks! |
👋🏼 Hi @andrewsykim This is Supriya, v1.22 enhancement shadow here. For the enhancement to be included in the 1.22 milestone, it must meet the following criteria: The KEP must have test plans Please make sure to follow all the instructions and update the KEP to include this. Thank you! |
Hi @andrewsykim, 1.22 Enhancements Lead here. 👋 With enhancements freeze now in effect we are removing this enhancement from the 1.22 release. Feel free to file an exception to add this back to the release. If you plan to do so, please file this as early as possible. Thanks! |
/remove-label lead-opted-in |
Hello 👋 1.30 Enhancements Lead here, I'm closing milestone 1.29 now, /milestone clear |
thanks for the reminder @salehsedghpour , i do not think we will have changes for 1.30. our plan is to make the next move to stable after 1.31. |
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 |
this issue is still relevant for tracking our progress, the plan is still targeting a stable release for 1.31 but this might change if we run into issues removing the final cloud provider bits from the tree. /remove-lifecycle stale |
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 |
i think we are nearing the end for this issue, it appears that we have completed all the checklists here. i think it would be appropriate to review the KEP again to ensure we are ready, or have already, moved to final release phase. /remove-lifecycle stale |
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 |
/remove-lifecycle stale the comment #2395 (comment) still stands |
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 |
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 |
i'm fairly certain we have reached the end for this issue, and i believe we can close it now. we just need to update the description to record that this went stable in 1.31. /remove-lifecycle rotten |
Enhancement Description
This is a proposal outlining steps to remove "in-tree" cloud provider code from the k8s.io/kubernetes repo while being
as least disruptive to end users and other Kubernetes developers as possible.
Discussion Link:
Primary contact (assignee): @andrewsykim @cheftako
Responsible SIGs: sig-cloud-provider
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Beta
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: