Christian Jürges

> While we're at it -- a full nextcloud k8s operator would be amazing ;). yeah - but only if the nextcloud docker image removes the rsync stuff and tries...

> The `/var/www/html` volume is defined in the base image and cannot be undefined. Nextcloud itself does not really work on read-only systems. The config is only one example, apps...

our solution on building customised one volume nextcloud docker images using symlinks, can be found here: https://gitlab.eqipe.ch/k8s/nextcloud-image/-/blob/main/Dockerfile-apache-one-data-volume.template?ref_type=heads We use several tricks to overcome the design flaws of the current nextcloud...

> Before the upgrade step is run, a list of active plugins is obtained. Then the upgrade step runs, and the list of active plugins is compared and the diff...

We also are running on k8s and we also did some modification by creating own docker image based on the official one. Thinking in the same direction as you like...

> > Was the backup created by v1.16.x Velero? > > I haven't updated or changed velero since the backup: > > ``` > ❯ velero version > Client: >...

The Problem occurs in internal/volume/volumes_information.go: there is a check ```golang // This is protective logic. The passed-in VS should be all related // to this backup. if volumeSnapshot.Labels[velerov1api.BackupNameLabel] != v.BackupName...

> > We see the same effect. Some Namespaces having "CSI Snapshots" filled with the snapshot details and some do not. > > Do you mean the backups are created...

> [@chrisamti](https://github.com/chrisamti) Ah, I see. The label length limitation is an issue in Velero usage. I will consider how to fix it in future. But it's possible to shorten the...