Describe the bug
Helm: ceph-csi-drivers chart fails to deploy when clientProfiles[0].rbd is defined, reporting that the value is null when they are actually defined. Removing the rbd section from clientProfiles resolves the issue but this may not be desirable for those who want to adjust values.
Environment details
- Image/version of ceph-csi-operator : 1.0.4
- Image/version of Ceph-CSI driver : 1.0.4
- Kubernetes cluster version : 1.36
- Ceph cluster version : N/A
Steps to reproduce
Steps to reproduce the behavior:
values.yaml
clientProfiles:
- name: "my-profile"
cephConnection:
name: "my-connection"
rbd:
radosNamespace: ""
cephCsiSecrets:
controllerPublishSecret:
name: my-secret
namespace: ceph-csi-operator-system
Actual results
Helm fails to deploy ceph-csi-drivers when following the respective values.yaml example.
Expected behavior
Helm should deploy ceph-csi-drivers
Logs
Warning UpgradeFailed 1s (x5 over 3m4s) helm-controller (combined from similar events): Helm upgrade failed for release ceph-csi-operator-system/ceph-csi-driver with chart ceph-csi-drivers@1.0.4: failed to create resource: server-side apply failed for object ceph-csi-operator-system/my-profile csi.ceph.io/v1, Kind=ClientProfile: ClientProfile.csi.ceph.io "my-profile" is invalid: [spec.rbd: Invalid value: "null": spec.rbd in body must be of type object: "null", <nil>: Invalid value: null: some validation rules were not checked because the object was invalid; correct the existing errors to complete validation]
Describe the bug
Helm: ceph-csi-drivers chart fails to deploy when clientProfiles[0].rbd is defined, reporting that the value is null when they are actually defined. Removing the rbd section from clientProfiles resolves the issue but this may not be desirable for those who want to adjust values.
Environment details
Steps to reproduce
Steps to reproduce the behavior:
values.yaml
Actual results
Helm fails to deploy ceph-csi-drivers when following the respective values.yaml example.
Expected behavior
Helm should deploy ceph-csi-drivers
Logs