- Expose a workload
- Expose and secure a workload
- Security
- Cannot connect to a service exposed by an APIRule
- External DNS management
Certificate management - Issuer not created
Symptom
When you try to create an Issuer CR using cert.gardener.cloud/v1alpha1, the resource is not created. There are no logs in the cert-management controller.
Cause
The Namespace in which the Issuer CR was created is incorrect. By default, the cert-management watches the default Namespace for all Issuer CRs.
Remedy
Make sure that you created the Issuer CR in the default Namespace. Run:
Click to copy
kubectl get issuers -AIf you want to create the Issuer CR in a different Namespace, adjust the cert-management settings during the installation.