Error on Kommander install: "no matches for kind "ClusterIssuer" " – D2iQ

When trying to install Kommander to a new DKP cluster, you may encounter an error that resembles the following:

failed to ensure "Kommander Root CA is deployed": failed creating root CA resources: could not read dir manifests: could not read dir rootca: callback returned an error: failed to patch resource from manifests/rootca/1_self-signed-issuer.yaml: failed to patch resource selfsigned-issuer (cert-manager.io/v1, Kind=ClusterIssuer): no matches for kind "ClusterIssuer" in version "cert-manager.io/v1"

Solution

The most common cause of this error is that you are trying to install Kommander to a cluster that is not yet self-managed.

To resolve this, follow the appropriate instructions in our documentation for making your DKP cluster self-managed before installing Kommander, depending on your provider:

AWS: https://docs.d2iq.com/dkp/latest/make-the-new-aws-cluster-self-managed

AWS Airgap: https://docs.d2iq.com/dkp/latest/make-air-gapped-aws-cluster-self-managed

Azure: https://docs.d2iq.com/dkp/latest/azure-make-new-cluster-self-managed

GCP: https://docs.d2iq.com/dkp/latest/make-the-new-gcp-cluster-self-managed

vSphere: https://docs.d2iq.com/dkp/latest/make-vsphere-cluster-self-managed

Pre-Provisioned: https://docs.d2iq.com/dkp/latest/pre-provisioned-make-cluster-self-managed