-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Flux fails to provision objects longer than 262144 chars #1962
Comments
Thanks for your report. Yes, Flux is using |
Experiencing the same issues around source controlled Grafana dashboards |
Same grafana dashboard import issue here... Is there a workaround available? I don't want to disable validation for the whole namespace. |
Same issue with Grafana dashboards and very big generated resources. This issue is not well referenced on Google so I'll link it to the relevant issue on: |
Can anyone on the current thread say whether this issue this issue would be continued on Flux v2? I haven't tried reproducing the issue yet, but if I understand I don't know enough about the implementation of kustomize controller or helm controller to say whether there is a similar issue or if it could still be a problem in the rewritten version. |
I will close the issue for now as it is stale. Flux v1 remains in maintenance mode. We can provide support to Flux v1 users especially with respect to migrating to the new Flux version, Flux v2, which has some breaking changes but is also a total rewrite and also brings many improvements. I'm closing the issue but you are most welcome to write back on this issue, or open another issue. Thanks for using Flux. |
I am seeing an error where Flux will fail to create a ConfigMap, complaining about the length of annotations. This configmap has a very large
data
section, presumably Flux is using akubectl apply
like 3-way merge and storing the last applied config in the annotations which is causing the upset.Can Flux fall back to a recreate or patch based on current and desired states only?
The text was updated successfully, but these errors were encountered: