What happened:
I do a helm install sucesfully, and then , do a helm upgrate unsucesfully, get error :
Error: UPGRADE FAILED: unable to build kubernetes objects from current release manifest: resource mapping not found for name: "my-release-helm-oncall" namespace: "" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
ensure CRDs are installed first
What did you expect to happen:
I will expect to make a succesfully helm upgrade.
However , if I do a new k8s install ( same versions that cluster that get me oncall update errors ) , and do a helm install with the same values, no get errors , make a succesfully installation and works fine.
How do we reproduce it?
you do a helm install
then do a helm upgrade
Grafana OnCall Version
all version from 1.2.34
Product Area
Helm
Grafana OnCall Platform?
Kubernetes
User's Browser?
N/A
Anything else to add?
However , if I do a new k8s install ( same versions that cluster that get me oncall update errors ) , and do a helm install with the same values, no get errors , make a succesfully installation and works fine.
manolooon
commented
8 months ago
What went wrong?
What happened: I do a helm install sucesfully, and then , do a helm upgrate unsucesfully, get error :
What did you expect to happen: I will expect to make a succesfully helm upgrade.
However , if I do a new k8s install ( same versions that cluster that get me oncall update errors ) , and do a helm install with the same values, no get errors , make a succesfully installation and works fine.
How do we reproduce it?
Grafana OnCall Version
all version from 1.2.34
Product Area
Helm
Grafana OnCall Platform?
Kubernetes
User's Browser?
N/A
Anything else to add?
However , if I do a new k8s install ( same versions that cluster that get me oncall update errors ) , and do a helm install with the same values, no get errors , make a succesfully installation and works fine.