Skip to content
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

Kubernetes 1.27 Deprecated CSIStorageCapacity: Storage.k8s.io/v1beta1: use v1. #437

Closed
MarkCupitt opened this issue Apr 24, 2023 · 5 comments
Assignees

Comments

@MarkCupitt
Copy link

What steps did you take and what happened:
Deployed zfs-localpv under Kubernetes 1.27

Pods would not schedule because PVs would not provision with error 0/1 nodes are available: 1 node(s) did not have enough free storage. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..

Openebs-zfs-controller had log entry

E0424 04:24:46.342908 1 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1beta1.CSIStorageCapacity: failed to list *v1beta1.CSIStorageCapacity: the server could not find the requested resource

1.27 Deprecations

CSIStorageCapacity: Storage.k8s.io/v1beta1: use v1.

https://sysdig.com/blog/kubernetes-1-27-whats-new/

@MarkCupitt
Copy link
Author

is this connected? #299

@MarkCupitt
Copy link
Author

image

OpenEBS Version 2.1.0

@vharsh
Copy link
Member

vharsh commented Jun 26, 2023

/assign @vharsh

@vharsh
Copy link
Member

vharsh commented Jun 27, 2023

This issue is coming because an older version of CSI provisioner is being used(3.0.0). The fix was pushed in https://github.com/kubernetes-csi/external-provisioner/pull/710. At a first glance it doesn't look to be coupled with a Kubernetes version which only supports v1-CSIStorageCapacity and it manages it internally and should not impact it's running & functionality on older Kubernetes clusters. However this needs to be validated once in the CI.

The fix for this would require bumping up the zfsController.provisioner.tag from v3.0.0 to v3.2.0. I'd take a stock of what other changes are being introduced and make relevant changes to the CI and then raise a fix for this.

@vharsh
Copy link
Member

vharsh commented Jul 26, 2023

got fixed in #461

@vharsh vharsh closed this as completed Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants