-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[2.10 RC] Namespace not created in ArgoCD v2.10.0-rc1 when using CreateNamespace syncOption #16829
Comments
Related (possibly duplicate): #13874 |
Thank you @hlastras for reporting this and the detailed description. I can also confirm this bug, we discussed this during the Argo Contributors meeting. We will get some eyes on this. |
I've tried searching for similar issues but missed the one you mentioned. My apologies. In our tests, the issue seems related but not identical. In our Interestingly, if I add the annotation Additionally, the issue you mentioned discusses a workaround by adding To summarize: v2.9.3:
v2.10.0-rc1:
I hope I've conducted the tests correctly. If not, apologies in advance 🙏 |
The issue seems to have caused after this specifc gitops-engine version upgrade. These 2 PRs in GitOps Engine project are the suspects |
reverting the PR argoproj/gitops-engine#546 seems to resolve the issue. Need to look deeper in the changes that is causing the error |
Root Cause:When server side apply is set to true, dry run is run in server mode, if the dry run fails in server mode, then it is re-run in client mode. But the server side apply is still set. This is not a supported configuration in
SolutionWhen
Created this PR argoproj/gitops-engine#563 for fixing this |
@hlastras This issue should be now addressed by argoproj/gitops-engine#564 |
Hi @leoluz Thank you very much for your quick work |
@hlastras Thank you for confirming and glad that it is working for you now. |
Description
We encountered an issue with ArgoCD
v2.10.0-rc1
where theApplication
resource doesn't create the required namespace whensyncPolicy.syncOptions
includesCreateNamespace=true
andServerSideApply=true
. It works if I remove optionServerSideApply=true
Steps to Reproduce:
Set up a local Kubernetes cluster using Kind (I've tested with version 1.27.x and 1.29.0).
Install ArgoCD v2.10.0-rc1 (following instructions from the release notes):
kubectl apply -f
:And it fails with the error
namespaces "helloworld" not found
This are part of the logs of the
ApplicationController
. On it, I can see it tries to create the Namespace, but any error.Observations:
ServerSideApply=true
fromsyncPolicy.syncOptions
in v2.10.0-rc1 resolves the issue.Expected Behavior:
The
Application
resource should create the specified namespace whenCreateNamespace=true
is set, as it does in version 2.9.3.The text was updated successfully, but these errors were encountered: