search

wave-k8s / wave

Kubernetes configuration tracking controller
Apache License 2.0
646 stars 82 forks source link

Helm chart installation fails on Kubernetes v1.23.6+k3s1 #125

Closed nifr closed 2 years ago

nifr commented 2 years ago

I tried to install wave with the following helm (v3) command:

helm upgrade \
   wave \
   wave \
   --repo='https://wave-k8s.github.io/wave/' \
   --version='2.0.0' \
   --namespace='wave' \
   --create-namespace \
   --install \
   --wait \
   --wait-for-jobs \
   --debug

Issue

The Helm chart installation fails with message:

Solution

Use version rbac.authorization.k8s.io/v1 instead of rbac.authorization.k8s.io/v1beta1 for ClusterRole and ClusterRolebinding resources.

Full Error Log

Error: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "wave-wave" namespace: "" from "": no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "wave-wave" namespace: "" from "": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first]
helm.go:84: [debug] [resource mapping not found for name: "wave-wave" namespace: "" from "": no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "wave-wave" namespace: "" from "": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"
ensure CRDs are installed first]
unable to build kubernetes objects from release manifest

Versions:

nifr commented 2 years ago

I moved on to use stakater/Reloader.