Upgrade to kube-prometheus-stack 34.x helm chart fails prerequisites

[rombert]

Hi,

I am managing an installation of the kube-prometheus-stack helm chart with flux. I am currently using version 33.2.0 and want to update to the latest - 34.8.0 .

The official instructions are to upgrade the CRDs first:

---

Run these commands to update the CRDs before applying the upgrade.

kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.55.0/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagerconfigs.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.55.0/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagers.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.55.0/example/prometheus-operator-crd/monitoring.coreos.com_podmonitors.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.55.0/example/prometheus-operator-crd/monitoring.coreos.com_probes.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.55.0/example/prometheus-operator-crd/monitoring.coreos.com_prometheuses.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.55.0/example/prometheus-operator-crd/monitoring.coreos.com_prometheusrules.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.55.0/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.55.0/example/prometheus-operator-crd/monitoring.coreos.com_thanosrulers.yaml

---

Each of these commands fails with the same error

error: Apply failed with 1 conflict: conflict with "helm-controller" using apiextensions.k8s.io/v1: .spec.versions
Please review the fields above--they currently have other managers. Here
are the ways you can resolve this warning:
* If you intend to manage all of these fields, please re-run the apply
  command with the `--force-conflicts` flag.
* If you do not intend to manage all of the fields, please edit your
  manifest to remove references to the fields that should keep their
  current managers.
* You may co-own fields by updating your manifest to match the existing
  value; in this case, you'll become the manager if the other manager(s)
  stop managing the field (remove it from their configuration).
See https://kubernetes.io/docs/reference/using-api/server-side-apply/#conflicts

I am not sure how to proceed here. Should I hope/trust that flux would do the right thing, since it seems to manage the CRDs? Or should I instead force an update and then try to fix the situation on the flux side?

[stefanprodan]

Unlike Helm, Flux does know how to upgrade CRDs. To enable CRDs upgrades for your HelmReleases see the docs here: https://fluxcd.io/docs/components/helm/helmreleases/#crds.

An example of kube-prometheus-stack can be found here https://github.com/fluxcd/flux2/blob/main/manifests/monitoring/kube-prometheus-stack/release.yaml, this is part of our monitoring solution for Flux https://fluxcd.io/docs/guides/monitoring/

[rombert]

Works great for me, thanks @stefanprodan