mimir icon indicating copy to clipboard operation
mimir copied to clipboard

Published 20 hours ago • verified publisher icon grafana

policy/v1beta1 removed in kubernetes 1.25

Open Siebjee opened this issue 2 years ago • 2 comments

Describe the bug

API policy/v1beta1 is removed in kubernetes 1.25. Now the HelmChart is now not compatible with 1.25

To Reproduce

  1. Deploy the helm chart mimir-distributed to a 1.25 / 1.26 kubernetes cluster.

Helm erros with:

Helm upgrade failed: unable to build kubernetes objects from current release manifest: resource mapping not found for name: "grafana-mimir" namespace: "grafana-mimir" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"...

Expected behavior

Successful helm deployment of grafana mimir.

Environment

  • Infrastructure: kubernetes (GKE) 1.26
  • Deployment tool: helm

Siebjee avatar Mar 01 '23 14:03 Siebjee

@Siebjee could you paste the output of helm template here? I just tested our mimir helm chart using kube version 1.26, I get the policy/v1 set correctly. I suspect there might be some path issues that make helm didn't pickup your correct kube version.

lamida avatar Mar 02 '23 11:03 lamida

@lamida I can't via helm template.. I can via helm get manifest as flux deploys it for me my local helm template might not produce the same thing. Both values.yaml and the manifest.yaml can be found here.

And I should not get any resources for PodSecurityPolicy as i have mimir.rbac.usePodSecurityPolicy set to false. Edit: Above statement about mimir.rbac.usePodSecurityPolicy is partially false. I mis interpreted the yaml. I solved this by rbac.create: false

⚠️ Please note: my initial attempt was on helm chart 3.3.0... I missed the memo. I need to reconfirm now i'm on 4.2.0.

Siebjee avatar Mar 02 '23 11:03 Siebjee

Hi, @Siebjee things should work fine equally in 4.2.0 too. Just to put a note again as @krajorama also already mentioned, Kind: PodSecurityPolicy wouldn't be created by mimir-distributed helm chart for Kubernetes 1.25+. All other resources policy apiVersion also will be dynamically set based on the Kubernetes version where the helm chart is going to be installed.

I will close this issue for now.

lamida avatar Mar 03 '23 03:03 lamida

I can confirm 4.2.0 works as intended. I believe my issue was a result of poor lifecycle management on my part.

Siebjee avatar Mar 03 '23 08:03 Siebjee