Cert-manager: No Resources found (Certificate, Issuer etc.) but everything works.

Created on 13 Dec 2019  路  2Comments  路  Source: jetstack/cert-manager

Bugs should be filed for issues encountered whilst operating cert-manager.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:
I'm not able to see the Certificates, Issuers etc.

Expected behaviour:
Show everything.

Steps to reproduce the bug:
Steps to reproduce the bug should be clear and easily reproducible to help people
gain an understanding of the problem.

> kubectl apply --validate=false -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.12/deploy/manifests/00-crds.yaml

> helm install \
  --name cert-manager \
  --namespace istio-system \
  --version v0.12.0 \
  jetstack/cert-manager

> helm install certificates . 
... 
> helm status certificates
LAST DEPLOYED: Thu Dec 12 17:16:16 2019
NAMESPACE: istio-system
STATUS: DEPLOYED

RESOURCES:
==> v1alpha2/Certificate
NAME                     AGE
xxxxxxx-cert  14h
xxxxxxx-cert    15h
telemetry-cert           44h

==> v1alpha2/Issuer
NAME                    AGE
certificate-dns-issuer  44h

Environment details::

  • Kubernetes version (e.g. v1.10.2): v1.14.8-gke.12
  • Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): GKE
  • cert-manager version (e.g. v0.4.0): 0.12.0
  • Install method (e.g. helm or static manifests): Helm

When I try to:

> kubectl get certificates --all-namespaces
No resources found.

I do not see anything, but the certificates are correctly generated, so everything seems to work, but I do not have visibility.

The CustomResourceDefinitions:

kubectl get CustomResourceDefinition --all-namespaces | grep cert
certificaterequests.cert-manager.io            2019-12-11T10:02:45Z
certificaterequests.certmanager.k8s.io         2019-12-09T14:01:30Z
certificates.cert-manager.io                   2019-12-11T10:02:45Z
certificates.certmanager.k8s.io                2019-12-09T14:01:29Z
challenges.acme.cert-manager.io                2019-12-11T10:02:45Z
challenges.certmanager.k8s.io                  2019-12-09T14:01:30Z
clusterissuers.cert-manager.io                 2019-12-11T10:02:46Z
clusterissuers.certmanager.k8s.io              2019-12-09T14:01:30Z
issuers.cert-manager.io                        2019-12-11T10:02:46Z
issuers.certmanager.k8s.io                     2019-12-09T14:01:30Z
managedcertificates.networking.gke.io          2019-12-09T13:31:39Z
orders.acme.cert-manager.io                    2019-12-11T10:02:46Z
orders.certmanager.k8s.io                      2019-12-09T14:01:30Z

All of them:

kubectl get CustomResourceDefinition --all-namespaces
NAME                                           CREATED AT
adapters.config.istio.io                       2019-12-09T13:59:48Z
attributemanifests.config.istio.io             2019-12-09T13:59:46Z
authorizationpolicies.security.istio.io        2019-12-09T13:59:48Z
backendconfigs.cloud.google.com                2019-12-09T13:31:11Z
capacityrequests.internal.autoscaling.k8s.io   2019-12-09T13:31:38Z
certificaterequests.cert-manager.io            2019-12-11T10:02:45Z
certificaterequests.certmanager.k8s.io         2019-12-09T14:01:30Z
certificates.cert-manager.io                   2019-12-11T10:02:45Z
certificates.certmanager.k8s.io                2019-12-09T14:01:29Z
challenges.acme.cert-manager.io                2019-12-11T10:02:45Z
challenges.certmanager.k8s.io                  2019-12-09T14:01:30Z
clusterissuers.cert-manager.io                 2019-12-11T10:02:46Z
clusterissuers.certmanager.k8s.io              2019-12-09T14:01:30Z
clusterrbacconfigs.rbac.istio.io               2019-12-09T13:59:46Z
destinationrules.networking.istio.io           2019-12-09T13:59:47Z
envoyfilters.networking.istio.io               2019-12-09T13:59:47Z
gateways.networking.istio.io                   2019-12-09T13:59:47Z
handlers.config.istio.io                       2019-12-09T13:59:48Z
httpapispecbindings.config.istio.io            2019-12-09T13:59:47Z
httpapispecs.config.istio.io                   2019-12-09T13:59:47Z
instances.config.istio.io                      2019-12-09T13:59:48Z
issuers.cert-manager.io                        2019-12-11T10:02:46Z
issuers.certmanager.k8s.io                     2019-12-09T14:01:30Z
managedcertificates.networking.gke.io          2019-12-09T13:31:39Z
meshpolicies.authentication.istio.io           2019-12-09T13:59:47Z
orders.acme.cert-manager.io                    2019-12-11T10:02:46Z
orders.certmanager.k8s.io                      2019-12-09T14:01:30Z
policies.authentication.istio.io               2019-12-09T13:59:47Z
quotaspecbindings.config.istio.io              2019-12-09T13:59:47Z
quotaspecs.config.istio.io                     2019-12-09T13:59:47Z
rbacconfigs.rbac.istio.io                      2019-12-09T13:59:47Z
rules.config.istio.io                          2019-12-09T13:59:47Z
scalingpolicies.scalingpolicy.kope.io          2019-12-09T13:31:39Z
serviceentries.networking.istio.io             2019-12-09T13:59:47Z
servicerolebindings.rbac.istio.io              2019-12-09T13:59:48Z
serviceroles.rbac.istio.io                     2019-12-09T13:59:48Z
sidecars.networking.istio.io                   2019-12-09T13:59:46Z
templates.config.istio.io                      2019-12-09T13:59:48Z
updateinfos.nodemanagement.gke.io              2019-12-09T13:31:39Z
virtualservices.networking.istio.io            2019-12-09T13:59:48Z

Any idea?

Thanks!

Most helpful comment

Try it
kubectl get certificate.cert-manager.io --all-namespaces
full name for crd certificate.cert-manager.io for v0.11+
for work kubectl get certificates --all-namespaces remove old crd with group 'certmanager.k8s.io' if you dont need old version cert-manager.
If the same resource is in different groups. kubernetes picks up by default from the group that deployed earlier.
your log:
certificaterequests.cert-manager.io 2019-12-11T10:02:45Z
certificaterequests.certmanager.k8s.io 2019-12-09T14:01:30Z
my log:
certificaterequests.cert-manager.io 2019-12-15T18:51:14Z
certificaterequests.certmanager.k8s.io 2020-01-21T04:19:32Z

All 2 comments

Why did you close this? As the same thing is happening with me as well.

Try it
kubectl get certificate.cert-manager.io --all-namespaces
full name for crd certificate.cert-manager.io for v0.11+
for work kubectl get certificates --all-namespaces remove old crd with group 'certmanager.k8s.io' if you dont need old version cert-manager.
If the same resource is in different groups. kubernetes picks up by default from the group that deployed earlier.
your log:
certificaterequests.cert-manager.io 2019-12-11T10:02:45Z
certificaterequests.certmanager.k8s.io 2019-12-09T14:01:30Z
my log:
certificaterequests.cert-manager.io 2019-12-15T18:51:14Z
certificaterequests.certmanager.k8s.io 2020-01-21T04:19:32Z

Was this page helpful?
0 / 5 - 0 ratings

Related issues

kragniz picture kragniz  路  4Comments

caiobegotti picture caiobegotti  路  4Comments

matthew-muscat picture matthew-muscat  路  4Comments

munnerz picture munnerz  路  4Comments

jbouzekri picture jbouzekri  路  4Comments