Sandro Mathys

No, I haven't. v1.15.8 is the latest we have anywhere at the moment. But I think I also haven't seen anything in the v1.16.0 or v1.16.1 changelogs that could have...

I simplified the naming slightly for this bug report, yea. Instead of `api` it should be `kubermatic-api` and instead of `dashboard` it should be `kubermatic-dashboard`. This is the `kubermatic` ingress...

New sysdump: https://drive.switch.ch/index.php/s/veVExBHdHLRgINE

Maybe more of a side note as I don't think this explains my problem but it's a first major difference I found between how ingress-nginx and Cilium handle the `defaultBackend`...

Yea, that's kind of what I meant - I think Kubernetes defined it vague enough such that ingress-nginx and Cilium are probably both conformant. But it should be fairly easy...

Alright, so back to my issue and bug report. In the new sysdump, we can find the `kubermatic` ingress in the file `ciliumingresses-20240829-135539.yaml`, here's its `spec`: ``` spec: defaultBackend: service:...

@sayboras any thoughts on my latest findings?

It's been a while 😬

I like the proposal, but please make sure it works for edge cases, such as: 1) velero is already installed on the source cluster, 2) source cluster is a UC...

This issue doesn't mention the range of choices. Please don't make it just time of the day (daily from xx:xx) but also at least let them choose the day(s) of...