Birk Bohne

> Why do we need the `alias: mysql_metrics`? Sorry, it's in the description. > > > alias added to keep the old chart dependency variable names and to avoid names...

> > > Why do we need the `alias: mysql_metrics`? Sorry, it's in the description. > > > > alias added to keep the old chart dependency variable names and...

> Will the service owner of designate correct the linting error first? > > ``` > Error: failed linting charts: failed building dependencies for chart "designate => (version: \"0.2.2\", path:...

closed because of review request bombing

> would you kindly rebase first to solve the conflicts ? i would prefer having less commits in the PR just to review the commit messages as well, which can...

@bashar-alkhateeb the `rebase and merge` option reports conflicts. The local interactive rebasing also shows conflicts for multiple commits. I think we should chose the `squash and merge` option to merge...

Superseded by https://github.com/sapcc/helm-charts/pull/6519

What about using `mariadb-dump ... | kopia snapshot create` for https://github.com/mariadb-operator/mariadb-operator/blob/c251ccd9894f8de08f2a361953c96da261c5d34d/pkg/command/backup.go#L135 to let `mariadb-dump` create consistent backups and than pipe them to `kopia` to be able to use all the...

I think you need both. Golang unit tests to validate your golang code before and independent from the usage in the Helm chart. Helm unit tests are very helpful to...

`helm-unittest` is doing a good job. You just need to define rules in Yaml without Helm template or golang knowledge required. Our [mariadb-galera](https://github.com/sapcc/helm-charts/tree/master/common/mariadb-galera) Helm chart relies heavily on Helm templating...