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
Is your feature request related to a problem? Please describe.
When a configmap / secret change and triggers a job to run from cronjob it does not set the owner reference metadata, so the job / pod is not connected to cronjob in any way. This is quite visible in ArgoCD for instance since you cannot see the job / pod that is created in the UI.
Describe the solution you'd like
Job manifest created from cronjob should set owner reference metadata to cronjob
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When a configmap / secret change and triggers a job to run from cronjob it does not set the owner reference metadata, so the job / pod is not connected to cronjob in any way. This is quite visible in ArgoCD for instance since you cannot see the job / pod that is created in the UI.
Describe the solution you'd like
Job manifest created from cronjob should set owner reference metadata to cronjob
The text was updated successfully, but these errors were encountered: