This way, shutdown hook of linkerd proxy sidecar container could be called after backup. This is important because endlessly-running sidecar prevents backup-job-pod from existing.
This would also be useful for something like nextcloud, which needs to be put into maintenance mode before backups and then taken out of maintenance mode after backups.
Summary
As a user of k8up backup operator, I would like to be able to specify a custom command that is executed AFTER backup is done.
This would allow implementation of solution 2 as described in https://itnext.io/three-ways-to-use-linkerd-with-kubernetes-jobs-c12ccc6d4c7c
This way, shutdown hook of linkerd proxy sidecar container could be called after backup. This is important because endlessly-running sidecar prevents backup-job-pod from existing.
Context
See https://itnext.io/three-ways-to-use-linkerd-with-kubernetes-jobs-c12ccc6d4c7c for detailed information
Out of Scope
No response
Further links
No response
Acceptance Criteria
No response
Implementation Ideas
No response