-
Notifications
You must be signed in to change notification settings - Fork 265
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
CreateApplicationEvent failure when App is in other namespace #847
Labels
bug
Something isn't working
Comments
jortkoopmans
added a commit
to EnergyExchangeEnablersBV/argocd-image-updater
that referenced
this issue
Aug 30, 2024
The other issue related to 'apps in any namespace': #601 |
jortkoopmans
added a commit
to EnergyExchangeEnablersBV/argocd-image-updater
that referenced
this issue
Sep 1, 2024
jortkoopmans
added a commit
to EnergyExchangeEnablersBV/argocd-image-updater
that referenced
this issue
Sep 2, 2024
Closed by #848 |
1 task
Tchoupinax
pushed a commit
to Tchoupinax/argocd-image-updater
that referenced
this issue
Oct 23, 2024
…-labs#847) (argoproj-labs#848) Signed-off-by: Jort Koopmans <jort.koopmans@entrnce.com> Signed-off-by: Tchoupinax <corentinfiloche@hotmail.fr>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When running (latest/master branch) updater, with Applications in other namespaces, Events will fail to be published, with a message like:
To Reproduce
Steps to reproduce the behavior:
Result is that the event is not published, this warning is logged instead.
Expected behavior
Events are published
Additional context
This is related to recent functionality on Apps in other namespaces.
Looking at the code, it seems to boil down to the kubernetes client being initiated in a particular namespace, which is not matching the Application.
I have a branch that resolves this issue (for me at least), which I will link to this issue for review.
Version
v0.14.0 and or built from master.
Logs
See above
The text was updated successfully, but these errors were encountered: