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.

Sign up for GitHub

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

Jump to bottom

Update to use v1.CSINode #385

Closed
msau42 opened this issue Dec 11, 2019 · 0 comments · Fixed by #383
Closed

Update to use v1.CSINode #385

msau42 opened this issue Dec 11, 2019 · 0 comments · Fixed by #383
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
2.0

Comments

@msau42
Copy link
Collaborator

msau42 commented Dec 11, 2019

This change will require a major version bump because we would have to bump the min K8s version to 1.17 when the object was introduced.

We should make this change at least 1, if not 2 releases before the v1beta gets removed from Kubernetes.

/lifecycle frozen
@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Dec 11, 2019
@msau42 msau42 added this to the 2.0 milestone Jan 30, 2020
@bertinatto bertinatto mentioned this issue Apr 17, 2020
Merged
kbsonlong pushed a commit to kbsonlong/external-provisioner that referenced this issue Dec 29, 2023
@k8s-ci-robot
Merge pull request kubernetes-csi#385 from humblec/cve
d5a3196 
Fix CVE, CSI spec update and update kube dependencies to latest.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
2.0
Development

Successfully merging a pull request may close this issue.

Use v1.CSINode in the external-provisioner bertinatto/external-provisioner
2 participants
@k8s-ci-robot @msau42