PodSecurityPolicy In Grafana Dependency

[BenjaminDavison]

What happened:

PodSecurityPolicy are currently still present in the Grafana helm chart Open Match relies on. Updating to later version should fix it.

helm install open-match --create-namespace --namespace open-match `
>> --set open-match-telemetry.enabled=true `
>> --set open-match-customize.enabled=true `
>> --set global.telemetry.grafana.enabled=true `
>> --set global.telemetry.jaeger.enabled=true `
>> --set global.telemetry.prometheus.enabled=true `
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "open-match-grafana" namespace: "" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
o matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
ensure CRDs are installed first]

What you expected to happen:

Open-Match to install.

How to reproduce it (as minimally and precisely as possible):

Run:

helm install open-match --create-namespace --namespace open-match `
>> --set open-match-telemetry.enabled=true `
>> --set open-match-customize.enabled=true `
>> --set global.telemetry.grafana.enabled=true `
>> --set global.telemetry.jaeger.enabled=true `
>> --set global.telemetry.prometheus.enabled=true

Output of kubectl version:

Client Version: v1.26.1
Kustomize Version: v4.5.7

Cloud Provider/Platform (AKS, GKE, Minikube etc.):

Minikube

Open Match Release Version:

1.7.0

Install Method(yaml/helm):

Helm

[joeholley]

@mridulji Can you have a look at what work would be required to update the grafana helm chart version? It's it's more than a simple version bump + validation, we'll likely sit on this for a while as we're evaluating moving from the grafana helm chart to the grafana operator.