Skip to content

Avoid null spec.valuesFrom in Feature templates - #1346

Merged
ArnobKumarSaha merged 1 commit into
masterfrom
arnob-null-valfrom
Sep 28, 2026
Merged

ArnobKumarSaha merged 1 commit into
masterfrom
arnob-null-valfrom

Conversation

@ArnobKumarSaha

Copy link
Copy Markdown
Member

On non-OpenShift clusters, 33 Feature templates in `opscenter-features` (and `cert-manager` in `ace-installer`) render a bare `valuesFrom:` → `null`. The Feature CRD types it as an array, so server-side apply fails:

spec.valuesFrom: Invalid value: "null": spec.valuesFrom in body must be of type array: "null"

Client-side apply (Helm v3) prunes the null, so this only surfaces with Helm v4 / helm-controller >= v1.5.0, which defaults new installs to SSA. Reproduced on vanilla kube-apiserver v1.35.0 and v1.36.2 (SSA fails, create succeeds on both).

Fix: move `valuesFrom:` inside the `distro.openshift` conditional; drop the always-empty one in cert-manager.

ace-installer-certified still needs regeneration via chart-packer.

Bare 'valuesFrom:' renders as null, which the apiserver rejects under
server-side apply (Helm v4 / helm-controller >= v1.5.0 default for new
installs). Client-side apply silently prunes it, hiding the bug.

Signed-off-by: Arnob Kumar Saha <arnob@appscode.com>
@ArnobKumarSaha
ArnobKumarSaha force-pushed the arnob-null-valfrom branch 3 times, most recently from 2cf6528 to e4925a3 Compare September 28, 2026 08:45
@ArnobKumarSaha
ArnobKumarSaha merged commit dddf8b4 into master Sep 28, 2026
6 of 8 checks passed
@ArnobKumarSaha
ArnobKumarSaha deleted the arnob-null-valfrom branch September 28, 2026 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant