André Bauer

We had the same problem with a lot of kustomizations and immutable CluserIP, volumname and stroageclass fields, updating from kustomize controller 0.14.1 to 0.20.2. ``` flux-system backstage False Service/backstage/patroni-metrics dry-run...

If you want to see the actual problematic fields you have to add "--show-managed-fields" to your kubectl command. See my post above for a workaround: https://github.com/fluxcd/flux2/issues/2386#issuecomment-1040102499 ``` kubectl -n ingress-nginx...

Building modues etc. on startup means also, that you need build tools in your container. So you end up with a production container, which hast gcc installed. See: https://github.com/strapi/strapi-docker/blob/master/base/alpine/Dockerfile#L4 From...

In favour :) The way it's done now is against container best practices.

Imho the point of the article is not that Liveness probes are dangerous per se. You just have to use them right. I even would go so far to say...

Same here. Imho helm-controller should act as "helm upgrade" command as this changes edited resources to it's desired state again.

Ok, i understand that continuously upgrading the helm chart would be a mess secretswise, but it would be nice anyway if one could force such upgrade via "flux reconcile helmrelease"...

I see the contantly on GKE at the moment. Especially if i try to recreate a cluster from scratch. All the flux pods are dying constantly, because k8s api can't...

I'm using the fluxcd terraform provider. Does it support altering this value? My pod args look like: ``` - args: - --events-addr=http://notification-controller/ - --watch-all-namespaces=true - --log-level=info - --log-encoding=json - --enable-leader-election...

Use the following command to also see charts in all namespaces and also the ones where installation is in progress. ``` helm list -Aa ```