RELEASED: Public: September 20, 2023
Resolved issues
- Storage class linked to persistent volume claim could be incorrect (BEE-37658)
-
The displayed storage class was the one in the controller configuration, but not the one actually used by the persistent volume claim. In case of underlying modifications on Kubernetes side, this could be incorrect.
The UI now displays the storage class that is actually used by the persistent volume claim, which can differ from the storage class declared in the controller configuration.