Annotate config, image, env and postgresql values

[mertbozfakioglu]

Stack 2/4. See #400 for the tooling and conventions.

What

Annotates the credential and database sections of values.yaml: nameOverride/fullnameOverride, config (license, encryption key, JWT, Google auth, external Postgres), image, initImage, env, environmentSecrets, environmentVariables, externalSecrets, and the postgresql subchart block.

This is the first PR where values.schema.json validates anything, so it bumps the minor version (6.13.0).

• Commented-out options become real keys with null values. Neither tool can see commented-out keys. null renders exactly like a missing key, while "" would not, because quote renders them differently.
• Types are as wide as the templates accept. Values rendered through quote take integers or strings (config.postgresql.port, dbConnectorTimeout, postgresPoolMaxSize). ssl_enabled takes a boolean or a string. Optional keys accept null.
• Enums only where Kubernetes would reject the value anyway (image.pullPolicy, secretStoreRef.kind).
• Unknown keys are still allowed.
• New documentation: image.pullSecrets was read by the templates but never mentioned in values.yaml. config.jwtSecret now notes that reusing the generated secret relies on Helm lookup, so Argo CD users should set it explicitly.

Testing

• compare-render.sh: all 35 ci/ values files render the same as main.
• main's full repo-root values.yaml, used as a user values file, passes the schema.

Reviewing

Only charts/retool/values.yaml is hand-written. Read the annotated sections in the file itself, since the diff is noisy. The schema, README and root values.yaml are generated.

🤖 Generated with Claude Code

[mertbozfakioglu]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Annotate probe, resource, scheduling and volume values #403
• Annotate service, ingress, httpRoute and networkPolicy values #402
• Annotate config, image, env and postgresql values #401 👈 (View in Graphite)
• Add generated values.schema.json and chart README tooling #400
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The change reaches teams using the Retool Helm chart.

Widen the two boolean-only schema entries before merging so existing values files can still upgrade.

Findings

1.  Quoted settings block upgrades ▶
2.  Docs understate supported fields ▶

_{Reviews (1) · Last reviewed commit: "Annotate config, image, env and postgres..." · Reviewed by Greptile}

[greptile-apps]

Quoted settings block upgrades

The new schema rejects config.useInsecureCookies: "false" and postgresql.ssl_enabled: "false", although both previously worked. Their templates use quote, so strings and booleans produce the same environment values. Existing values files, including values passed through --set-string, now fail Helm validation before an upgrade can render.

Add [boolean, string] annotations for both settings in values.yaml and regenerate the schema, matching config.postgresql.ssl_enabled.

[greptile-apps]

Docs understate supported fields

The new description says env cannot express valueFrom.fieldRef, but retool.env already passes through every map field other than value, including nested valueFrom.fieldRef. This gives operators a false reason to move settings into environmentVariables.

Describe it as an alternative list of full Kubernetes EnvVar entries, then regenerate the documentation.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!