You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
We have Argo Events Sensors creating Jobs with generateName. Argo CD is configured with application.resourceTrackingMethod=annotation, so it expects argocd.argoproj.io/tracking-id. But that ID requires the final resource name, which isn’t known with generateName.
Is there any supported way to have these runtime Jobs show up under the Argo CD application tree without switching global tracking to label?
We tried setting ownerReferences (static Sensor UID), but it’s brittle and breaks on redeploy.
Any recommended pattern?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We have Argo Events Sensors creating Jobs with generateName. Argo CD is configured with application.resourceTrackingMethod=annotation, so it expects argocd.argoproj.io/tracking-id. But that ID requires the final resource name, which isn’t known with generateName.
Is there any supported way to have these runtime Jobs show up under the Argo CD application tree without switching global tracking to label?
We tried setting ownerReferences (static Sensor UID), but it’s brittle and breaks on redeploy.
Any recommended pattern?
Beta Was this translation helpful? Give feedback.
All reactions