fix(catalyst-platform): escape literal Helm-curly in api-deployment.yaml comment (#699)
Helm parses the entire file (including YAML comments) for template
directives BEFORE YAML parsing strips comments. Literal '{{ ... }}'
inside a # comment was treated as a template directive and failed
with 'unexpected <.> in operand' at line 419.
PR #698 introduced this in the explanatory comment for the
SOVEREIGN_FQDN ConfigMap workaround. Reword to avoid the literal
double-curlies — the comment still describes the constraint without
tripping the Helm parser.
Co-authored-by: hatiyildiz <hatice@openova.io>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
7edc4370a3
commit
2146deb427
@ -416,9 +416,9 @@ spec:
|
||||
# via bp-catalyst-platform OCI chart) AND by Kustomize (contabo-
|
||||
# mkt's clusters/contabo-mkt/apps/catalyst-platform Kustomization
|
||||
# at path: ./products/catalyst/chart/templates). Kustomize parses
|
||||
# raw YAML — Helm template syntax `{{ ... }}` here breaks the
|
||||
# Kustomize build (caught live on contabo 2026-05-03 from
|
||||
# commit adf8dc7d: "yaml: invalid map key: {.Values.global...}").
|
||||
# raw YAML — Helm template syntax (double-curly directives) here
|
||||
# breaks the Kustomize build (caught live on contabo 2026-05-03
|
||||
# from commit adf8dc7d: "yaml: invalid map key").
|
||||
#
|
||||
# Solution: read the value from a ConfigMap that exists ONLY on
|
||||
# Sovereigns (not contabo). On contabo the optional reference
|
||||
|
||||
Loading…
Reference in New Issue
Block a user