-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
SharedResourceWarning Errors when Argo is self managing Umbrella type applications. #5614
Comments
In any case, it's unrelated to Rollouts so transferred the issue |
Hi, I found out that in this context, 2 different specs conflicting for the same resource did not actually resolve to the last one syncing. |
We've come across this issue, and after some debugging found out that on the spec of a Leaving this here for future reference on googling people :) |
Summary
Encountered a setup which creates all sorts of problems.
I created an Umbrella application (Argo Application CRD referencing itself and other Applications from a folder path).
The reason for this setup is that Umbrella app is reading all the Application manifests from single folder, which further spawns the entire graph of dependencies.
I don't know if this type of setup is bad because it's poorly documented anywhere.
Has this been encountered by anyone else?
What happened/what you expected to happen?
I'm updating the umbrella app values which get read by downstream components.
After renaming Umbrella app by mistake, both applications are now conflicting and entire system is toast.
Argo components are stuck without possibility to sync/delete any resources.
Argo Application resource status fields show the following:
Diagnostics
What version of Argo Rollouts are you running?
argo-rollouts:v0.10.2
Paste the logs from the argo-server controller
Paste the logs from the rollout controller
Thank you, cheers!
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: