Moritz Rieger

Thanks for your fast response @feikesteenbergen 1. Did you change the value in the ConfigMap manually? -> no 2. Did you do a helm upgrade after changing the values? ->...

Thanks for the explanation, now this makes sense to me. But I still wonder why the values from tstune never take effect, even the ones that don't require a restart...

Sorry for the confusion, when I said: > But I still wonder why the values from tstune never take effect, even the ones that don't require a restart and are...

Thanks @feikesteenbergen ! We already worked around this issue and just set all parameters from timescaledb-tune explicitly in `dcs.postgresql.parameters` followed by a patronictl restart. But I set the cluster back...

@timoreimann > This seems unrelated to your PR and must have slipped through to master. The linting issue occurs only in the CI because set-up go installs the latest minor...

Should we close this PR? @varshavaradarajan @timoreimann

I am also trying to close the Feedback Loop from Flux to GitLab. Unfortunately, GitLab doesn't provide any action on a commit status change 😔. Another option would be to...

AFAIU, the procedure would be the same for multi-region keys from a sops perspective. Multi-region keys share the same KeyID, but the region portion of the ARN differs for every...

Will there be a `flux diff helmrelease` to see the diff of the templated output of helm-controller? We are currently doing this in a bash script and it would be...

Thanks, will check with the new image. Because the new external-dns requires a `company-` prefix, I deleted all existing related TXT records and created them with the prefix and new...