Replies: 2 comments
-
|
There seems to be something with my git repo that is causing this. If I changed the path to a new "clean" path where there were no previously created kustomization.yml file, it works. I will close this as something unique to my environment. But it would still be helpful to know how to see the Kustomize generated manifest that was causing the errors in the Kustomize-controller. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Well, maybe I spoke too soon. It worked to reconcile without errors a few times then started giving the same error I saw before. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm running into a problem that I'm having trouble debugging.
After installing a new instance of Flux v2 into our EKS cluster, I'm getting this error in the kustomize-controller logs:
I can't figure out how to see what the generated manifest is to debug the problem.
When I run
kustomize buildlocally, it looks fine. Even runningkustomize build | kubectl apply --dry-run=client -f-locally shows everything seems to be fine. I've tried this without any kustomizations other than the ones automatically generated by the flux install.Is there a way I can run
flux reconcile kustomization --with-source flux-system --verbosein such a way to keep the generated manifest that the kustomize-controller generates to inspect it?I'm using:
I'm attaching what gets generated locally with
kustomize buildBeta Was this translation helpful? Give feedback.
All reactions