Found while installing keda v2.20.1-5 with a private registry secret.
values.schema.json types imagePullSecrets entries as strings, but the pod templates render the value verbatim into pod specs, where Kubernetes requires objects:
- Passing the object form fails schema validation: helm errors with "at '/imagePullSecrets/0': got object, want string".
- Passing the string form passes the schema but renders an invalid PodSpec:
imagePullSecrets:
- ghcr-kedify
which the API server rejects (entries must be {name: ...}).
So the feature is unusable without --skip-schema-validation plus the object form (verified working on helm 3.21). Fix either direction: type the schema entries as objects with a name property, or keep string entries and map them to {name: .} in the templates. Upstream kedacore charts use the object form, so the schema is probably the side to change.
Found while installing keda v2.20.1-5 with a private registry secret.
values.schema.json types imagePullSecrets entries as strings, but the pod templates render the value verbatim into pod specs, where Kubernetes requires objects:
which the API server rejects (entries must be {name: ...}).
So the feature is unusable without --skip-schema-validation plus the object form (verified working on helm 3.21). Fix either direction: type the schema entries as objects with a name property, or keep string entries and map them to {name: .} in the templates. Upstream kedacore charts use the object form, so the schema is probably the side to change.