Skip to content

Commit

Permalink
Add alert CDIMultipleDefaultVirtStorageClasses
Browse files Browse the repository at this point in the history
Signed-off-by: Alex Kalenyuk <[email protected]>
  • Loading branch information
akalenyu authored and sradco committed Nov 16, 2023
1 parent e00262f commit 1e0049f
Showing 1 changed file with 32 additions and 0 deletions.
32 changes: 32 additions & 0 deletions docs/runbooks/CDIMultipleDefaultVirtStorageClasses.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# CDIMultipleDefaultVirtStorageClasses
<!-- Edited by akalenyu, 10 Oct 2023 -->

## Meaning

This alert fires when more than one default virtualization storage class exists.

A default virtualization storage class has precedence over a default Kubernetes storage class for creating a VirtualMachine disk image.

## Impact

If more than one default virtualization storage class exists, a data volume that requests a default storage class (storage class not explicitly specified), receives the most recently created one.

## Diagnosis

Obtain a list of default virtualization storage classes by running the following command:

```bash
$ kubectl get sc -o json | jq '.items[].metadata|select(.annotations."storageclass.kubevirt.io/is-default-virt-class"=="true")|.name'
```

## Mitigation

Ensure that only one storage class has the default virtualization storage class annotation.

<!--DS: If you cannot resolve the issue, log in to the link:https://access.redhat.com[Customer Portal] and open a support case, attaching the artifacts gathered during the Diagnosis procedure.-->
<!--USstart-->
If you cannot resolve the issue, see the following resources:

- [OKD Help](https://www.okd.io/help/)
- [#virtualization Slack channel](https://kubernetes.slack.com/channels/virtualization)
<!--USend-->

0 comments on commit 1e0049f

Please sign in to comment.