Migrate the Helm chart from version 4.x to 5.0
The mimir-distributed
Helm chart version 5.0 and later does not install PodSecurityPolicy objects on Kubernetes version 1.24 by default to prepare for upgrade to Kubernetes version 1.25.
Prerequisite
- This procedure is only applicable if
rbac.create
istrue
andrbac.type
ispsp
in your current Helm values. This was the case by default before Helm chart version 5.0.
Procedure
- If
rbac.create
isfalse
orrbac.type
isscc
, then there is nothing to do, skip the whole procedure. - Choose between the following options:
- If you are on Kubernetes version 1.22 or later and already have Pod Security Admission set up, you don’t need to do anything and can upgrade to Helm chart version 5.0.
- If you are on Kubernetes version 1.22 or later but don’t have Pod Security Admission set up and want to upgrade to Kubernetes version 1.25 after this procedure, then follow the Migrate to Kubernetes version 1.25 guide.
- If you are on Kubernetes version 1.24 and want to keep using PodSecurityPolicy, then merge the following setting into your custom values file:
rbac: forcePSPOnKubernetes124: true
Warning
Usingrbac.forcePSPOnKubernetes124
equaltrue
value prevents you from upgrading to Kubernetes version 1.25.