Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kustomization resources are silently dropped if there is an extra space after --- #371

Open
alex-berger opened this issue Jun 23, 2021 · 2 comments
Assignees
Labels
area/kustomize Kustomize related issues and pull requests bug Something isn't working

Comments

@alex-berger
Copy link

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 ---).

--- 
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: HelmRepository
metadata:
  name: linkerd2-edge
  namespace: flux-system
spec:
  interval: 10m
  url: https://helm.linkerd.io/edge
---
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: HelmRepository
metadata:
  name: linkerd2-stable
  namespace: flux-system
spec:
  interval: 10m
  url: https://helm.linkerd.io/edge-stable

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.

@kingdonb kingdonb added area/kustomize Kustomize related issues and pull requests bug Something isn't working labels Jul 8, 2021
@kingdonb
Copy link
Member

kingdonb commented Jul 8, 2021

Yes, this is definitely related to fluxcd/flux2#1522 – thanks for the report

@kingdonb kingdonb self-assigned this Jul 22, 2021
@kingdonb
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kustomize Kustomize related issues and pull requests bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants