Kidswiss

A side effect of this: it enables the user to do one shot backups with `k8up backup --namespace my-app --from-schedule my-schedule`.

@jenwirth Currently we don't provide such options. Two options for this would come to my mind: * add a `support istio` flag to the CRDs which sets the command *...

Hi @seanhamlin Thanks for bringing this to our attention. 30 prebackup pods in a single namespace are quite a lot. In your linked issue you're writing about spreading the pods...

Hi @seanhamlin Do you have any feedback for my questions above?

We have an internal ticket for implementing label selectors for the job CRDs. The idea is that you could define a label selector for a job object which will only...

dang I thought I linked to the docs :) That selector already exists: `appuio.ch/backup=false` See the getting started tutorial: https://k8up.io/docs/0.1.5/getting-started.html

Is it possible to move these things into separate namespaces then? That don't contain a backup schedule at all? E.g. prometheus to a monitoring namespace, appX in the appXnamespace. etc....

One thought I just had: If we do this, should we provide a stable deduplication for this? Example: A new`scheduleB` is not registered because `scheduleA` is already registered. Both contain...

I had another idea over the weekend: We could hash the repository string and the type and use that as the randomness seed (https://golang.org/pkg/math/rand/#Seed). So each type and repo combination...

Sure we can use something else to generate the times, `rand` was just a suggestion. But I feel like we'd have to get the randomness for the same types and...