k8up
k8up copied to clipboard
k8up-io
Tell backupcommand in which container it should run
Summary
As user of K8up I want to control in which container of a Pod the backupcommand runs So that I'm sure it runs in the correct container.
Context
The backupcommand runs by default in the first container of a Pod. This imposes that one has control over the order of containers in a Pod and makes it impossible to run a backupcommand in the correct container if the order doesn't match.
We should provide a way to control in which container the backupcommand gets executed.
Out of Scope
No response
Further links
No response
Acceptance Criteria
No response
Implementation Ideas
An annotation which allows to specify the name of the container in which the backupcommand should be executed. E.g. k8up.io/backupcommand-container.
Absolutely required. I just migrated from Velero to K8up, as K8up only backups pvc data, which works better with a GitOps approach. However I now stuck on this issue, as I haven't (easy?) control over the container order provided by Helm charts.
As workaround I think about using kubectl in a Pre-Backup pod, which then will call the backup command on the target pod and proper container. However - this is additional effort and requires additonal resources, like role/sa/rolebinding for running kubectl.
However - K8up rocks! ( I just miss the Velero CLI, with which I can list and restore backups from scheduled, previously backup runs. )
Hi @vfolk30
Yes the feature has been released yesterday with K8up 2.7. https://github.com/k8up-io/k8up/releases/tag/v2.7.0
So I'm closing here.
