Error: unable to build kubernetes objects from release manifest

[ghost]

Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "AuthService" in version "getambassador.io/v3alpha1", unable to recognize "": no matches for kind "Mapping" in version "getambassador.io/v3alpha1", unable to recognize "": no matches for kind "RateLimitService" in version "getambassador.io/v3alpha1"]

about

I'm submitting this more as a resolved issue we encountered when installing via helm than an actual issue. It would probably be better to have this as a section of an FAQ, but I couldn't find a better place to put it that's discoverable via search engine. A few months ago we trialed out Ambassador and determined it was something we wanted to use. We uninstalled the old trial version likely in an improper fashion by deleting the namespace rather than helm uninstall or kubectl delete, and that left behind the lint of the old Ambassador customResourceDefinitions. When we went to reinstall, we followed the directions for a new installation since we thought that the old installation was completely gone, but the presence of the old CRDs gave us the aforementioned error message.

solution

Deleting all the older Ambassador CRDs and re-running the helm install command resolved the issue for us.

[pongchan666]

similar issue encounter using helm install edge-stac in microk8s.