Version:
PMM version: 2.35.0
Helm: pmm:1.2.0
Error:
helm upgrade --history-max=5 --install=true --namespace=percona --timeout=10m0s --values=/home/shell/helm/values-pmm-1.2.0.yaml --version=1.2.0 --wait=true pmm /home/shell/helm/pmm-1.2.0.tgz
checking 7 resources for changes
Patch ServiceAccount "pmm-service-account" in namespace percona
Looks like there are no changes for Secret "pmm-service-account-token"
Looks like there are no changes for ConfigMap "pmm"
Looks like there are no changes for ClusterRole "pmm"
Patch ClusterRoleBinding "pmm" in namespace
error updating the resource "pmm":
cannot patch "pmm" with kind ClusterRoleBinding: ClusterRoleBinding.rbac.authorization.k8s.io "pmm" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"ClusterRole", Name:"cluster-admin"}: cannot change roleRef
Looks like there are no changes for Service "monitoring-service"
Patch StatefulSet "pmm" in namespace percona
Error: UPGRADE FAILED: cannot patch "pmm" with kind ClusterRoleBinding: ClusterRoleBinding.rbac.authorization.k8s.io "pmm" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"ClusterRole", Name:"cluster-admin"}: cannot change roleRef
I just tried to update it with:
pmmEnv:
DISABLE_UPDATES: "1"
ENABLE_DBAAS: "1"
Any ideas on how this got borked? It was recently just installed yesterday. I haven’t done anything funky after installing.
FYI:
TL;DR
Helm 3, RKE 2 Cluster - installs and works perfectly fine… but can’t update the config once installed.
I’m going to guess I will have issues when updating the Helm Chart for the next version as well…