Cert-manager: Unable to find issuer

Created on 25 Jan 2018  ·  3Comments  ·  Source: jetstack/cert-manager

Hey,
I'm getting this error:

I0125 21:03:33.119601       1 controller.go:147] ingress-shim controller: syncing item 'default/at-consumer-platform-ingress-external'
E0125 21:03:33.119630       1 controller.go:156] ingress-shim controller: Re-queuing item "default/at-consumer-platform-ingress-external" due to error processing: clusterissuer.certmanager.k8s.io "letsencrypt-staging" not found

But I definately have an issuer....:

❯ k get issuer letsencrypt-staging -o yaml
apiVersion: certmanager.k8s.io/v1alpha1
kind: Issuer
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"certmanager.k8s.io/v1alpha1","kind":"Issuer","metadata":{"annotations":{},"name":"letsencrypt-staging","namespace":"default"},"spec":{"acme":{"email":"[email protected]","http01":{},"privateKeySecretRef":{"name":"letsencrypt-staging"},"server":"https://acme-staging.api.letsencrypt.org/directory"}}}
  clusterName: ""
  creationTimestamp: 2018-01-25T21:02:58Z
  generation: 0
  initializers: null
  name: letsencrypt-staging
  namespace: default
  resourceVersion: "333456"
  selfLink: /apis/certmanager.k8s.io/v1alpha1/namespaces/default/issuers/letsencrypt-staging
  uid: 1edb2e3e-0213-11e8-b5c2-42010a840219
spec:
  acme:
    email: [email protected]
    http01: {}
    privateKeySecretRef:
      key: ""
      name: letsencrypt-staging
    server: https://acme-staging.api.letsencrypt.org/directory
status:
  acme:
    uri: https://acme-staging.api.letsencrypt.org/acme/reg/5446219
  conditions:
  - lastTransitionTime: 2018-01-25T21:02:58Z
    message: The ACME account was registered with the ACME server
    reason: ACMEAccountRegistered
    status: "True"
    type: Ready

Any ideas? GKE 1.8.6, cert-manager 0.2.3

Most helpful comment

All 3 comments

It looks like you've specified kind: ClusterIssuer on your Certificate
resource, but you've created an Issuer instead (which is constrained to a
single namespace).

You need to either update your ingress-shim to use an Issuer instead of a
ClusterIssuer by default, or otherwise change your Issuer into a
ClusterIssuer.

Take a look at the Cluster Issuer user guide for more info:
https://github.com/jetstack/cert-manager/blob/master/docs/user-guides/cluster-issuers.md
On Thu, 25 Jan 2018 at 21:04, Karl Stoney notifications@github.com wrote:

Hey,
I'm getting this error:

I0125 21:03:33.119601 1 controller.go:147] ingress-shim controller: syncing item 'default/at-consumer-platform-ingress-external'
E0125 21:03:33.119630 1 controller.go:156] ingress-shim controller: Re-queuing item "default/at-consumer-platform-ingress-external" due to error processing: clusterissuer.certmanager.k8s.io "letsencrypt-staging" not found

But I definately have an issuer....:

❯ k get issuer letsencrypt-staging -o yaml
apiVersion: certmanager.k8s.io/v1alpha1
kind: Issuer
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"certmanager.k8s.io/v1alpha1","kind":"Issuer","metadata":{"annotations":{},"name":"letsencrypt-staging","namespace":"default"},"spec":{"acme":{"email":"[email protected]","http01":{},"privateKeySecretRef":{"name":"letsencrypt-staging"},"server":"https://acme-staging.api.letsencrypt.org/directory"}}}
clusterName: ""
creationTimestamp: 2018-01-25T21:02:58Z
generation: 0
initializers: null
name: letsencrypt-staging
namespace: default
resourceVersion: "333456"
selfLink: /apis/certmanager.k8s.io/v1alpha1/namespaces/default/issuers/letsencrypt-staging
uid: 1edb2e3e-0213-11e8-b5c2-42010a840219
spec:
acme:
email: [email protected]
http01: {}
privateKeySecretRef:
key: ""
name: letsencrypt-staging
server: https://acme-staging.api.letsencrypt.org/directory
status:
acme:
uri: https://acme-staging.api.letsencrypt.org/acme/reg/5446219
conditions:

  • lastTransitionTime: 2018-01-25T21:02:58Z
    message: The ACME account was registered with the ACME server
    reason: ACMEAccountRegistered
    status: "True"
    type: Ready

Any ideas?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/issues/280, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbPy-oSnJw_9oe-SS0XliPsi4oQbGJks5tOOx4gaJpZM4RtfHA
.

I'm going to close this issue now, but feel free to re-open if you are still running into issues.

/close

Was this page helpful?
0 / 5 - 0 ratings