Removing In-Tree Cloud Providers #2395
Comments
k8s-ci-robot
added
the
needs-sig
|
Migrating all the old template keps to new template : #2391 |
|
/assign |
|
/sig cloud-provider |
k8s-ci-robot
added
sig/cloud-provider
annajung
added
tracked/yes
|
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 |
annajung
added
tracked/no
|
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! |
annajung
removed
the
tracked/yes
JamesLaverack
added
the
tracked/yes
|
👋🏼 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! |
|
@dims has started collecting migration notes here, kubernetes/kubernetes#120411 and i've opened a PR to update the metadata, although i'm not sure why it's failing currently, #4190 |
|
updated the description here to reflect our goal of a 1.29 beta release. we still need to update the checklist here, i think we've done all the alpha steps but we need to round up the PRs to link there. |
|
as per our discussion in slack, i am adding the /label lead-opted-in |
|
@elmiko: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads] In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
elmiko
added
the
lead-opted-in
|
/milestone v1.29 |
|
Hello @shekhar-rajak 👋, v1.29 Enhancements team here. Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
|
Hi @shekhar-rajak and @elmiko 👋, v1.29 Communication Release Team. I would like to check any plan about publication blogs related new features, removals, and deprecations for this release. The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review) |
|
@rayandas should i updating the checklist in your post? |
|
Sure, go ahead. @elmiko |
|
ok, one more follow up before i start checking things. does it need to be merged for us to mark them as complete? (i notice the last item specifically mentions it) |
|
@elmiko You can update the issue description with open PRs and when it’s merged you can update the checklist, or I’ll update it. So yes things should be merged before. |
|
@rayandas perfect, thanks. i'll need to do a little research as it appears the description is out-of-date with our current work. |
|
@rayandas updated the description, does that look ok? |
|
Hi @shekhar-rajak @elmiko 👋🏽 checking in once more as we approach the 1.29 enhancement freeze deadline on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as |
|
thanks @rayandas , that is accurate. i have a feeling we might miss this freeze given that i am having trouble finding some of the requested information from review. |
|
With KEP PR #4190 approved, the enhancement is ready for the enhancements freeze. The status is now marked as |
|
Hey there @elmiko, @bridgetkromhout and @andrewsykim ! 👋, v1.29 Docs team shadow here. |
|
@Princesso i believe all of our documentation for this change is already live on the kube docs website. |
|
@elmiko, could you kindly point me to a PR for reference purposes? Thank you! |
|
@Princesso i believe these are the PRs that introduced the docs, although one of them might have older PRs that i couldn't find easily. |
|
Hey again @shekhar-rajak 👋, 1.29 Enhancements team here, Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023: . Here's where this enhancement currently stands:
With all this, the status of this KEP is now Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks! |
|
Hi @elmiko @bridgetkromhout @andrewsykim, I'm reaching out from the 1.29 comms team 👋 Are you all planning to write a blog for this feature? If so, please create a placeholder blog PR in https://github.com/kubernetes/website. The deadline for creating a placeholder PR is today 11/14, so please let us know if you are planning to write a blog as soon as possible. Thanks! cc: @Priyankasaggu11929 |
|
@a-mccarthy would love to have a blog article, but none of us have had time to write it or even propose the placeholder. i'm not sure if there is a path forward for us on this issue, any guidance? |
Hi @elmiko please try to submit the placeholder, to help you, the feature blog are released after the release date (Dec 5th) |
|
placeholder submitted, kubernetes/website#44010 |
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: