The k8s driver has CLEANUP_JOBS which controls if the job and secret created by the driver should be immediately deleted after the job completes. I would like to have another setting, OWNER_REFERENCES, which allows me manage resource cleanup via cascading deletes and have more control over when they are deleted, giving me time to troubleshoot failed jobs for example.
Resources created by the driver (jobs, secrets) should include the specified owner references.
The format of the OWNER_REFERENCES environment variable should be a json serialized representation of metav1.OwnerReference. For example,
The k8s driver has CLEANUP_JOBS which controls if the job and secret created by the driver should be immediately deleted after the job completes. I would like to have another setting, OWNER_REFERENCES, which allows me manage resource cleanup via cascading deletes and have more control over when they are deleted, giving me time to troubleshoot failed jobs for example.
Resources created by the driver (jobs, secrets) should include the specified owner references.
The format of the OWNER_REFERENCES environment variable should be a json serialized representation of
metav1.OwnerReference
. For example,