-
Notifications
You must be signed in to change notification settings - Fork 182
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
Update kustomize/api to v0.7.2 and disable kyaml #241
Conversation
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you provide information on what this change incorporates and how it fixes the issue referenced to in the PR? Either in-code or in the commit message.
ccf4f02
to
5a37e19
Compare
Workaround for upstream bug: kubernetes-sigs/kustomize#3446 Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
5a37e19
to
085588b
Compare
// buildKustomization wraps krusty.MakeKustomizer with the following settings: | ||
// - disable kyaml due to critical bugs like: | ||
// - https://github.com/kubernetes-sigs/kustomize/issues/3446 | ||
// - https://github.com/kubernetes-sigs/kustomize/issues/3480 | ||
// - reorder the resources just before output (Namespaces and Cluster roles/role bindings first, CRDs before CRs, Webhooks last) | ||
// - load files from outside the kustomization.yaml root | ||
// - disable plugins except for the builtin ones | ||
// - prohibit changes to resourceIds, patch name/kind don't overwrite target name/kind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
This PR updates
kustomize/api
to v0.7.2 and disableskyaml
when running kustomize build due to upstream bugs:Note that when
kyaml
is enabled,Kustomizer.Run
fails withError: json: unsupported type: map[interface {}]interface {}
without any hint to which object caused the error, making it impossible for Flux users to track down the incompatible manifest.Also if a manifest contains duplicate keys, kyaml panics thus crashing the whole controller 😢
Fix: fluxcd/flux2#729
Fix: #243