Kasten Operator 8.5.0 (Openshift) cannot open "WorkerPodCRDs".

I deployed Kasten Operator version 8.5.0 in my OpenShift 4.20 environment and created a K10 instance through Operator; however, the "WorkerPodCRDs.enabled" configuration is not working.

My configuration:

spec:
  auth:
    basicAuth:
      enabled: false
      htpasswd: ''
      secretName: ''
    openshift:
      dashboardURL: 'https://k10-route-kasten-io.apps.ocp4.corp.com/k10'
      enabled: true
      insecureCA: false
      openshiftURL: 'https://api.ocp4.corp.com:6443'
    tokenAuth:
      enabled: false
  global:
    genericVolumeSnapshot:
      enabled: true
    persistence:
      catalog:
        size: ''
      storageClass: ''
  metering:
    mode: airgap
  route:
    enabled: true
    host: ''
    tls:
      enabled: true
  workerPodCRDs:
    defaultActionPodSpec: test-spec
    enabled: true

It was discovered that this parameter was not enabled in k10-configmap; instead, "workerPodResourcesCRD.enabled" was incorrectly enabled.

Further analysis of Katen's Operator revealed that the template mapping appeared to be incorrect.

sh-5.1$ grep -r "workerPodCRDs" helm-charts/k10/templates/
helm-charts/k10/templates/_helpers.tpl:{{- if .Values.workerPodCRDs.resourcesRequests.maxMemory }}
helm-charts/k10/templates/_helpers.tpl:workerPodMaxMemoryRequest: {{ .Values.workerPodCRDs.resourcesRequests.maxMemory | quote }}
helm-charts/k10/templates/_helpers.tpl:{{- if .Values.workerPodCRDs.resourcesRequests.maxCPU }}
helm-charts/k10/templates/_helpers.tpl:workerPodMaxCPURequest: {{ .Values.workerPodCRDs.resourcesRequests.maxCPU | quote }}
helm-charts/k10/templates/_helpers.tpl:{{- if .Values.workerPodCRDs.resourcesRequests.maxEphemeralStorage }}
helm-charts/k10/templates/_helpers.tpl:workerPodEphemeralStorage: {{ .Values.workerPodCRDs.resourcesRequests.maxEphemeralStorage | quote }}
helm-charts/k10/templates/_helpers.tpl:{{- if .Values.workerPodCRDs.defaultActionPodSpec }}
helm-charts/k10/templates/_helpers.tpl:workerPodDefaultAPSName: {{ .Values.workerPodCRDs.defaultActionPodSpec | quote }}
helm-charts/k10/templates/_k10_container.tpl:{{- if .Values.workerPodCRDs.resourcesRequests.maxMemory }}
helm-charts/k10/templates/_k10_container.tpl:{{- if .Values.workerPodCRDs.resourcesRequests.maxCPU }}
helm-charts/k10/templates/_k10_container.tpl:{{- if .Values.workerPodCRDs.resourcesRequests.maxEphemeralStorage }}
helm-charts/k10/templates/_k10_container.tpl:        {{- if .Values.workerPodCRDs.enabled }}
helm-charts/k10/templates/_k10_container.tpl:            {{- if .Values.workerPodCRDs.defaultActionPodSpec }}
helm-charts/k10/templates/k10-config.yaml:  workerPodResourcesCRDEnabled: {{ .Values.workerPodCRDs.enabled | quote }}

Based on this result, the issue appears to be with the Katen Operator, indicating that configuration parameters are not being mapped correctly.

I also checked the actual parameters of Helm in the environment, and they were indeed not changed;

[liguoqiang@jump-linux openshift]$ oc -n kasten-io get secret sh.helm.release.v1.k10.v6 -o jsonpath='{.data.release}' | base64 -d | base64 -d | gzip -d | jq '.chart.values' |grep -A 10 workerPodCRDs
  "workerPodCRDs": {
    "defaultActionPodSpec": "",
    "enabled": false,
    "resourcesRequests": {
      "maxCPU": "",
      "maxEphemeralStorage": "",
      "maxMemory": ""
    }
  },
  "workerPodMetricSidecar": {
    "enabled": true,

I need this CRD because I require customization of the workerpod's network and limits.