-
Notifications
You must be signed in to change notification settings - Fork 614
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
Image update automation is modifying the kustomization yaml file format from mutliple line to a single line. #3284
Image update automation is modifying the kustomization yaml file format from mutliple line to a single line. #3284
Comments
Not just kustomization files, it seems to be doing this to other yaml files too, in particular ConfigMap. It is converting "human-readable" multi-line yaml to very human-unreadable strings with embedded newlines. |
Hello, I have the same issue on the HelmRelease, I tried to put a embedded yaml in the values of the HelmRelease, it format it as a single line string which make the embedded yaml not human-readable |
having the same issue too |
Randomly having the same issue. |
xref: fluxcd/flux2#3284 Signed-off-by: Stefan Prodan <[email protected]>
This has been fixed in fluxcd/image-automation-controller#605 and will be included in the Flux v2.2.0 release. |
Great news :) @stefanprodan when is 2.2.0 expected to be released? Thank you. |
See #4410 |
xref: fluxcd/flux2#3284 Signed-off-by: Stefan Prodan <[email protected]>
Describe the bug
Noticed that the image update automation is modifying the kustmization yaml file format from multi lines to a single line.
due to that reason updating the kustomization yaml file is not in sync with git.
Example:
Steps to reproduce
N/A
Expected behavior
Expected format should be as below
Screenshots and recordings
No response
OS / Distro
CentOS Linux release 7.7.1908 (Core)
Flux version
flux: v0.35.0
helm-controller: v0.25.0
image-automation-controller: v0.26.0
image-reflector-controller: v0.22.0
kustomize-controller: v0.29.0
notification-controller: v0.27.0
source-controller: v0.30.0
Flux check
flux check
► checking prerequisites
✗ flux 0.35.0 <0.36.0 (new version is available, please upgrade)
✔ Kubernetes 1.22.13-gke.1000 >=1.20.6-0
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.25.0
✔ image-automation-controller: deployment ready
► ghcr.io/fluxcd/image-automation-controller:v0.26.0
✔ image-reflector-controller: deployment ready
► ghcr.io/fluxcd/image-reflector-controller:v0.22.0
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v0.29.0
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v0.27.0
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v0.30.0
► checking crds
✔ alerts.notification.toolkit.fluxcd.io/v1beta1
✔ buckets.source.toolkit.fluxcd.io/v1beta2
✔ gitrepositories.source.toolkit.fluxcd.io/v1beta2
✔ helmcharts.source.toolkit.fluxcd.io/v1beta2
✔ helmreleases.helm.toolkit.fluxcd.io/v2beta1
✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2
✔ imagepolicies.image.toolkit.fluxcd.io/v1beta1
✔ imagerepositories.image.toolkit.fluxcd.io/v1beta1
✔ imageupdateautomations.image.toolkit.fluxcd.io/v1beta1
✔ kustomizations.kustomize.toolkit.fluxcd.io/v1beta2
✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2
✔ providers.notification.toolkit.fluxcd.io/v1beta1
✔ receivers.notification.toolkit.fluxcd.io/v1beta1
✔ all checks passed
Git provider
No response
Container Registry provider
gcr
Additional context
N/A
Code of Conduct
The text was updated successfully, but these errors were encountered: