Heads Up: Renaming of conditions on the KubeVirt Custom Resource

[Marc Sluiter]

Hello everybody,

today we merged a PR [0], which renamed the condition types on the KubeVirt custom resources.

This was done for alignment of conditions of all components in the KubeVirt ecosystem, which are deployed by the Hyperconverged Cluster Operator (HCO)[1], in order to make it easier for HCO to determine the deployment status of these components. The conditions are explained in detail in [2].

For KubeVirt this means that especially the "Ready" condition was renamed to "Available". This might affect you in case you used the "Ready" condition for waiting for a successful deployment of KubeVirt. If so, you need to update the corresponding command to something like `kubectl -n kubevirt wait kv kubevirt --for condition=Available`.

The second renamed condition is "Updating". This one is named "Progressing" now.

As explained in [2], there also is a new condition named "Degraded".

The "Created" and "Synchronized" conditions are unchanged.

These changes take effect immediately if you are deploying KubeVirt from the master branch, or starting with the upcoming v0.20.0 release.

[0] https://github.com/kubevirt/kubevirt/pull/2548

[1] https://github.com/kubevirt/hyperconverged-cluster-oocs/conditions.mdperator

[2] https://github.com/kubevirt/hyperconverged-cluster-operator/blob/master/docs/conditions.md

Best regards,

Marc Sluiter

He/Him/His

Senior Software Engineer

Red Hat

mslu...@redhat.com    

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,

Commercial register: Amtsgericht Muenchen, HRB 153243,

Managing Directors: Charles Cachera, Michael O'Neill, Tom Savage, Eric Shander    

@redhatjobs   redhatjobs @redhatjobs