-
Notifications
You must be signed in to change notification settings - Fork 6.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
Remove openstack feature gate and legacy in-tree provider documentation #10879
Conversation
|
Welcome @LarssonOliver! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: LarssonOliver The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @LarssonOliver. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Conflict with #10448 |
You're right. Sorry about that. The in-tree provider documentation is probably not needed anymore either which that one does not cover. I'll close this and open a new PR that only covers that. |
Redid this pr without the conflict in #10889 |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Removes documentation about the legacy in-tree OpenStack provider (removed 1.26) and the following feature gates:
CSIMigration
(removed 1.26)CSIMigrationOpenStack
(removed 1.25)ExpandCSIVolumes
(removed 1.26)Removed feature gate list
Specifying the feature gates as suggested by current documentation causes the kubelet to error out.
Which issue(s) this PR fixes:
Fixes #10250
Special notes for your reviewer:
Does this PR introduce a user-facing change?: