Tigera-operator helm chart unable to set csiNodeDriverDaemonSet resource memory/cpu requests & limits about operator HOT 5 CLOSED

Tried both suggested containers names with helm but both give the error suggestions the support value is csi-node-driver"

Error: UPGRADE FAILED: release calico failed, and has been rolled back due to atomic being set: cannot patch "default" with kind Installation: Installation.operator.tigera.io "default" is invalid: spec.csiNodeDriverDaemonSet.spec.template.spec.containers[0].name: Unsupported value: "calico-csi": supported values: "csi-node-driver"

Error: UPGRADE FAILED: release calico failed, and has been rolled back due to atomic being set: cannot patch "default" with kind Installation: Installation.operator.tigera.io "default" is invalid: spec.csiNodeDriverDaemonSet.spec.template.spec.containers[0].name: Unsupported value: "csi-node-driver-registrar": supported values: "csi-node-driver"

from operator.

I've created projectcalico/calico#8883 in the repo where the helm chart comes from because this is a helm chart issue, not an operator functionality issue. I'm going to close this issue. If you believe there is an operator issue here please comment and I can re-open this.

from operator.

You've not used a correct container name, see the docs for the allowed container names (calico-csi or csi-node-driver-registrar).

I'm not sure why we still allowed csi-node-driver as an allowed value, I'm guessing it was so we didn't break anything for someone that has used that as a container name, it was allowed before and if we removed it from the allowed values then a previously functioning config would have resulted in errors.

from operator.

You've not used a correct container name, see the docs for the allowed container names (calico-csi or csi-node-driver-registrar).

I'm not sure why we still allowed csi-node-driver as an allowed value, I'm guessing it was so we didn't break anything for someone that has used that as a container name, it was allowed before and if we removed it from the allowed values then a previously functioning config would have resulted in errors.

Perhaps the reason this cannot be set might be due to this line in the chart? https://github.com/projectcalico/calico/blob/master/charts/tigera-operator/crds/operator.tigera.io_installations_crd.yaml#L6869

from operator.

Yeah it seems the source of the helm chart has not pulled in the proper updates from this repo. You can see the expected allowed values in this repo here https://github.com/tigera/operator/blob/master/api/v1/csi_node_driver.go#L28

from operator.