Description
Hello!
deploy/kubernetes/overlays/stable-master appears to be a convenient way to deploy gcp-compute-persistent-disk-csi-driver. We used this as a remote base when initially deploying it and pinned to a particular commit hash.
However trying to update it is proving difficult because of the inconsistency of versions and absence of images the manifests reference.
As an example I wanted to update to v1.17.2 - which appears to be a stable Github release. But the image that is built via Kustomize is v1.15.0 https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/v1.17.2/deploy/kubernetes/images/stable-master/image.yaml#L55 .
If you want to build the Kustomize base with v1.17.2 image version, you need to reference v1.17.3 tag: https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/v1.17.3/deploy/kubernetes/images/stable-master/image.yaml#L54C12-L54C19 .
But this image doesn't even exist under that name, as the latest available is v1.15.4 - https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/images/k8s-staging-cloud-provider-gcp/images.yaml#L54 .
One of the reasons using a Kustomize base like this is attractive to us, is because its a simple way to see/receive new RBAC permissions that are required and/or new flags that are are added to components.
Thank you.