Common Error Messages

Some of the errors messages commonly encountered during installation and operations of Consul API Gateway are listed below, along with suggested methods for resolving them.

If the error message is not listed on this page, it may be listed on the main Consul Common errors page. If the error message is not listed on that page either, please consider following our general Troubleshooting Guide or reach out to us in Discuss.

Helm installation failed: “no matches for kind”

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "GatewayClass" in version "gateway.networking.k8s.io/v1alpha2", unable to recognize "": no matches for kind "GatewayClassConfig" in version "api-gateway.consul.hashicorp.com/v1alpha1"]

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "GatewayClass" in version "gateway.networking.k8s.io/v1alpha2", unable to recognize "": no matches for kind "GatewayClassConfig" in version "api-gateway.consul.hashicorp.com/v1alpha1"]

Conditions: When this error occurs during the process of installing Consul API Gateway, it is usually caused by not having the required CRD files installed in Kubernetes prior to installing Consul API Gateway.

Impact: The installation process will typically fail after this error message is generated

Recommended Action: Install the required CRDs by using the command in Step 1 of the Consul API Gateway installation instructions and then retry installing Consul API Gateway.