Describe the feature you'd like to have.
Change the controller code to use the v1 version of VolumeSnapshot instead of v1beta1.
What is the value to the end user? (why is it a priority?)
It appears that the v1beta1 API is going to be removed in kube 1.24, meaning that VolSync will no longer work for 1.24+ without this change.
How will we know we have a good solution? (acceptance criteria)
Additional context
Today, we use v1beta1 which means that VolSync is usable on Kubernetes versions 1.17 - 1.23 (although we only test back to 1.19).
When we make this change, we will require a minimum Kubernetes version of 1.20 (when v1 became available). While upstream Kube no longer supports the older versions, OCP, AKS, and GKE still support the equivalent of 1.19 until later this year.
JohnStrunk
commented
2 years ago
Describe the feature you'd like to have. Change the controller code to use the v1 version of VolumeSnapshot instead of v1beta1.
What is the value to the end user? (why is it a priority?) It appears that the v1beta1 API is going to be removed in kube 1.24, meaning that VolSync will no longer work for 1.24+ without this change.
How will we know we have a good solution? (acceptance criteria)
Additional context Today, we use v1beta1 which means that VolSync is usable on Kubernetes versions 1.17 - 1.23 (although we only test back to 1.19). When we make this change, we will require a minimum Kubernetes version of 1.20 (when v1 became available). While upstream Kube no longer supports the older versions, OCP, AKS, and GKE still support the equivalent of 1.19 until later this year.