You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to find an alternative way of attribution. Or make sure none of our environments use the built-in storage classes anymore.
storageclass.storage.k8s.io "premium-rwo" deleted
Error from server (AlreadyExists): storageclasses.storage.k8s.io "premium-rwo" already exists
storageclass.storage.k8s.io "premium-rwo" deleted
error: timed out waiting for the condition
storageclass.storage.k8s.io "premium-rwo" deleted
storageclass.storage.k8s.io/premium-rwo replaced
storageclass.storage.k8s.io "standard-rwo" deleted
Error from server (AlreadyExists): storageclasses.storage.k8s.io "standard-rwo" already exists
storageclass.storage.k8s.io "standard-rwo" deleted
Error from server (AlreadyExists): storageclasses.storage.k8s.io "standard-rwo" already exists
storageclass.storage.k8s.io "standard-rwo" deleted
Error from server (AlreadyExists): storageclasses.storage.k8s.io "standard-rwo" already exists
storageclass.storage.k8s.io "standard-rwo" deleted
error: timed out waiting for the condition
storageclass.storage.k8s.io "standard-rwo" deleted
Error from server (AlreadyExists): storageclasses.storage.k8s.io "standard-rwo" already exists
Looks like our storage class labeling does not work anymore in GKE 1.27
Idea: install kyverno in all dev/CI environments (should be mostly already the case), add a policy that prevents us from using the built-in GKE storage classes. Create our own storage classes. We already have e2e-default but duplicate the network attached built-ins from GKE and use those with correct attribution and labelling.
Fixes#7745
This is a pre-requisite for starting to test Kubernetes >= 1.27 on GKE
* create copies of built-in classes with the right labels for disk GC
* create a kyverno policy to prevent the use of the built-in ones
* updates bk agent to have latest version of gcloud
We need to find an alternative way of attribution. Or make sure none of our environments use the built-in storage classes anymore.
Looks like our storage class labeling does not work anymore in GKE 1.27
Originally posted by @pebrc in #7743 (comment)
The text was updated successfully, but these errors were encountered: