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

Storage class parameter update stopped working with k8s 1.27 on GKE #7745

Closed
pebrc opened this issue Apr 24, 2024 · 1 comment · Fixed by #7817
Closed

Storage class parameter update stopped working with k8s 1.27 on GKE #7745

pebrc opened this issue Apr 24, 2024 · 1 comment · Fixed by #7817
Assignees
@pebrc
Labels
:ci Things related to Continuous Integration, automation and releases >test Related to unit/integration/e2e tests

Comments

@pebrc
Copy link
Collaborator

pebrc commented Apr 24, 2024

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

Originally posted by @pebrc in #7743 (comment)
@pebrc pebrc added :ci Things related to Continuous Integration, automation and releases >test Related to unit/integration/e2e tests labels Apr 24, 2024
pebrc added a commit that referenced this issue Apr 24, 2024
@pebrc
Bump GKE version in tests to 1.26, AKS 1.29 (#7743)
1b1c4d9 
Update to more recent versions blocked by #7745 and #7746
@pebrc
Copy link
Collaborator Author

pebrc commented Apr 25, 2024 •
edited

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.

@pebrc pebrc mentioned this issue May 16, 2024
Merged
3 tasks
@pebrc pebrc self-assigned this May 17, 2024
pebrc added a commit that referenced this issue May 17, 2024
@pebrc
Stop recreating GKE storage classes (#7817)
3d524df 
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pebrc pebrc

Labels
:ci Things related to Continuous Integration, automation and releases >test Related to unit/integration/e2e tests
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Stop recreating GKE storage classes pebrc/cloud-on-k8s
1 participant
@pebrc