-
Notifications
You must be signed in to change notification settings - Fork 166
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
KubeVirt switch init of StorageClass from annotations to seed configuration #11689
Closed
hdurand0710 opened this issue
Jan 16, 2023
· 3 comments
· Fixed by #11701, kubermatic/kubevirt-csi-driver-operator#10, #11716 or kubermatic/dashboard#5569
Closed
KubeVirt switch init of StorageClass from annotations to seed configuration #11689
hdurand0710 opened this issue
Jan 16, 2023
· 3 comments
· Fixed by #11701, kubermatic/kubevirt-csi-driver-operator#10, #11716 or kubermatic/dashboard#5569
Labels
sig/virtualization
Denotes a PR or issue as being assigned to SIG Virtualization.
Milestone
Comments
hdurand0710
added
the
sig/virtualization
Denotes a PR or issue as being assigned to SIG Virtualization.
label
Jan 16, 2023
Re-opening as other PRs to come. |
Re-opening as other PRs to come. |
Re-opening as other PRs to come. |
This was referenced Jan 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the init of StorageClasses in the user cluster is done by adding some annotations to the wanted Storage Classes in the KubeVirt infra cluster:
kubevirt-initialization.k8c.io/initialize-sc : true
As a user, I want to change this mechanism and be able to configure in the
seed
the list of Storage Classes (from the infra cluster) that will be initialised into the user cluster.No backward compatibility is needed.
The text was updated successfully, but these errors were encountered: