RELEASED: Public: September 4, 2024
Resolved issues
- When changing the value of the storage class name using Configuration as Code bundles, the incorrect value of the storage class name is shown on the controller provisioning screen (BEE-51616)
-
When using Configuration as Code to provision controllers, every controller item in the bundle may need to be updated by specifying the
storageClassNameattribute for eachclusterEndpointsandkubernetesobjects. For example:
masterprovisioning: kubernetes: storageClassName: "nfs" clusterEndpoints: - id: ... jenkinsUrl: ... name: ... storageClassName: "nfs"