-
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 deprecated flag for Cinder CSI controllerplugin #6358
Remove deprecated flag for Cinder CSI controllerplugin #6358
Conversation
Hi @StevenReitsma. 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. |
10394b0
to
a4d868e
Compare
You mean that these changes will make leader-election-type always to endpoints until it is changed by the CSI driver? |
Sorry, I initially removed the deprecated flag for the csi-provisioner as well but noticed afterwards that the default is still |
I see, the new version doesn't know what is the |
Exactly! I pushed another bugfix to this PR: the csi-attacher now needs Looks like the change in #6221 wasn't really tested 😄 |
Add proper RBAC for new csi-attacher version
0bc82b1
to
6686def
Compare
/ok-to-test |
@alijahnas would you mind taking another look after I made some additional changes? Thanks again. |
/lgtm |
@StevenReitsma |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miouge1, StevenReitsma The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* 'master' of https://github.com/kubernetes-sigs/kubespray: Add a way to deploy cilium alongside another CNI (kubernetes-sigs#6373) Cleanup old build-cephfs-provisioner.yml playbook (kubernetes-sigs#6418) Always enable GitLab CI artifacts for cluster-dump (kubernetes-sigs#6412) Remove allow-release-candidate-upgrades already include in experimental-upgrades flag (kubernetes-sigs#6349) add calico-node selinux (kubernetes-sigs#6359) Add oomichi to reviwers of MetalLB addon (kubernetes-sigs#6393) Respect kube_override_hostname during removal/upgrade (kubernetes-sigs#6347) Fixed fedora modular repos activation for fcos (kubernetes-sigs#6300) Fix kube-proxy post deployment removal (kubernetes-sigs#5554) Remove old csi-attacher flag and fix RBAC for Cinder CSI (kubernetes-sigs#6358) Update cilium minimum kernel preinstall check (kubernetes-sigs#6376) Add readiness probe to dns-autoscaler (kubernetes-sigs#6382) Add Fedora CoreOS kubevirt image for tests (kubernetes-sigs#6337) allow kubeadm to upgrade etcd (kubernetes-sigs#6345) crio: harden downloads with retry (kubernetes-sigs#6374) Add workaround with include_task for mitogen (kubernetes-sigs#6312)
…sigs#6358) Add proper RBAC for new csi-attacher version
What type of PR is this?
/kind bug
What this PR does / why we need it:
#6221 broke the Cinder CSI plugin because a flag is being used that was removed
Special notes for your reviewer:
The
--leader-election-type
flag in thecsi-attacher
container is unsupported from the current version. It's deprecated incsi-provisioner
, but the default there is stillEndpoints
instead ofLease
so I guess we have to wait for the removal to change it.See: https://github.com/kubernetes-csi/external-attacher
Does this PR introduce a user-facing change?: