When using the operator in a meshed environment, e.g. linkerd, the jobs will never finish, as the proxy sidecar container does not end. In consequence, the operator will never see the backup job finishing - and not allow to start new backups as former one is still "active".
This could be solved when the operator inherits / applies an annotation to the backup jobs, that will prevent the mesh injection.
Use-Case
Using the operator with backups in a service meshed environment like linkerd or istio
Is this a feature you are interested in implementing yourself?
Proposal
When using the operator in a meshed environment, e.g. linkerd, the jobs will never finish, as the proxy sidecar container does not end. In consequence, the operator will never see the backup job finishing - and not allow to start new backups as former one is still "active". This could be solved when the operator inherits / applies an annotation to the backup jobs, that will prevent the mesh injection.
Use-Case
Using the operator with backups in a service meshed environment like linkerd or istio
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response