Closed tpo closed 4 months ago
You forgot to set a name for your installation
helm install wave wave-k8s/wave -n wave-system
You forgot to set a name for your installation
helm install wave wave-k8s/wave -n wave-system
Yes, or use --generate-name
. My suggestion is to add --generate-name
to the documentantion, so that the project has working install instructions in the README.
@tpo That is not wave-specific. It is basic helm usage. However, that PR should be easy enough.
❯ helm install wave wave-k8s/wave -n wave-system
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/alexjones/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/alexjones/.kube/config
Error: INSTALLATION FAILED: 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]
What am I doing wrong ?
@AlexsJones I'd suggest to open a new ticket. I think this is not the same problem as the origial one in this thicket.
Looks like we have to apply the CRDs ourselves as part of the installation, however it's not mentioned clearly that the helm chart won't install these.. which is a bit confusing as I would hope most people are using RBAC these days and expect these to be a part of the helm chart.
This issue has been inactive for 60 days. If the issue is still relevant please comment to re-activate the issue. If no action is taken within 7 days, the issue will be marked closed.
Not stale, just not actioned. This is still a problem.
@github-actions this was not completed. This is still a problem and helm installation does not work.
This doesn't work: