Kidswiss

@ccremer Sure we could start with the easier approach and get some actual real life experience on the impact.

@ccremer I assume this is obsolete now as v2 has been released quite a while ago?

Hi @vring0 Could you please provide the information requested by ccremer? Otherwise it's not possible for us to help you with the issues you're having.

@vring0 Do you still encounter this issue with Kubernetes 1.23+? According to https://github.com/k8up-io/k8up/issues/554 it seems to work with 1.23.

@shreddedbacon Thanks for the explanation. One thing about storing all snapshots in one CR: etcd has a limit of 1Mb per object. I believe for the really huge repos this...

Personal opinion incoming: Not sure if it's something that k8up should handle. Alerting rules are something very use case specific. The use case you have may not apply for all...

I'd also suggest to stop calling them defaults but rather examples. As they only work for schedules that are once a day as you've found out.

I'd opt for other metrics and keep the counter. One idea (which will probably bring its own share of issues no doubt): We could leverage the built in job monitoring...

I feel like the definition of `@nightly` can be very different for many users. For you it's 00:00 - 03:00 for me it would be more like 22:00 - 06:00....

@cdchris12 I'm rewriting your request a bit, to incorporate the information from the comments.