Skip to content

Don't apply csi-driver from k3s image #12550

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.

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

Merged
merged 1 commit into from
Aug 31, 2022
Merged

Don't apply csi-driver from k3s image #12550

merged 1 commit into from
Aug 31, 2022

Conversation

vulkoingim
Copy link
Contributor

@vulkoingim vulkoingim commented Aug 31, 2022

Description

In preview envs we use rook, so there's no need to apply the one from the image.

storage        csi-gce-pd-controller-6956df9894-jnn2w       0/5     ContainerCreating   0              10m
storage        csi-gce-pd-node-99hgn                        0/2     CrashLoopBackOff    14 (91s ago)   10m

Release Notes

NONE

Werft options:

  • /werft with-preview

@vulkoingim vulkoingim force-pushed the aa/fix-cloud-init-ns branch from 11ca046 to de402ff Compare August 31, 2022 14:31
@vulkoingim vulkoingim changed the title Create storage namespace for prev env in cloud-init Don't apply csi-driver from k3s image Aug 31, 2022
@roboquat roboquat merged commit 521afcc into main Aug 31, 2022
@roboquat roboquat deleted the aa/fix-cloud-init-ns branch August 31, 2022 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants