You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I upgraded from FluxCD version v0.13.4 to version v0.15.3 and suddenly some of our HelmRepository created (and owned) by a Kustomization disappeared despite them still being part of that Kustomization. After some analysis I figured out that actually all resources which had extra spaces (' ') after the YAML --- sequences where silently dropped without any warning or error in the logs. In the following example the linkerd2-edge was silently dropped as it contained an extra space in --- and linkerd-stable was not dropped (as it contains no extra space after ---).
I assume this is some kind of bug related to YAML parsing. Maybe this is another breaking change resulting from switching to Kustomize V4 (fluxcd/flux2#1522) or go-yaml.
The text was updated successfully, but these errors were encountered:
I'm going to look through sig-cli/kustomize for any open issues related to this report and try to link them back, so we can know when this is unblocked.
Today I upgraded from FluxCD version
v0.13.4
to versionv0.15.3
and suddenly some of ourHelmRepository
created (and owned) by aKustomization
disappeared despite them still being part of thatKustomization
. After some analysis I figured out that actually all resources which had extra spaces (' '
) after the YAML---
sequences where silently dropped without any warning or error in the logs. In the following example thelinkerd2-edge
was silently dropped as it contained an extra space in---
andlinkerd-stable
was not dropped (as it contains no extra space after---
).I assume this is some kind of bug related to YAML parsing. Maybe this is another breaking change resulting from switching to Kustomize V4 (fluxcd/flux2#1522) or go-yaml.
The text was updated successfully, but these errors were encountered: