opened
kyprifog
username_0
No matter what I do I always end up with a self signed cert using the following syntax:
```
apiVersion: cert-manager.io/v1alpha2
kind: Certificate
metadata:
  name: service-tls-cert
  namespace: service 
spec:
  dnsNames:
    - <DOMAIN>
  secretName: service-tls-cert
  issuerRef:
    name: letsencrypt-prod

```

```
apiVersion: cert-manager.io/v1alpha2
kind: ClusterIssuer
metadata:
  name: letsencrypt-prod
spec:
  acme:
    # The ACME server URL
    server: https://acme-v02.api.letsencrypt.org/directory
    # Email address used for ACME registration
    email: <EMAIL>
    # Name of a secret used to store the ACME account private key
    privateKeySecretRef:
      name: letsencrypt-prod
    solvers:
    # An empty 'selector' means that this solver matches all domains
    - selector: {}
      http01:
        ingress:
          class: nginx
```

```
helm upgrade \
  cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --set ingressShim.defaultIssuerName=letsencrypt-prod \
  --set ingressShim.defaultIssuerKind=ClusterIssuer \
  --set installCRDs=true \
```

This results in a self signed cert when I go to access <DOMAIN> instead of the CA issuer cert made by letsencrypt-prod.   Nothing unusual or relevant shows up in the cert-manager pod logs.
Issuer is ignored, results in self signed cert no matter what
issue
created
kyprifog
username_0
I'm finding this:
```
kubectl describe certificaterequests.cert-manager.io --namespace service

Status:
  Conditions:
    Last Transition Time:  2020-11-19T22:45:00Z
    Message:               Referenced "Issuer" not found: issuer.cert-manager.io "letsencrypt-prod" not found
    Reason:                Pending
    Status:                False
    Type:                  Ready
```
comment
created
kyprifog
username_0
I think this answered my issue:  https://stackoverflow.com/questions/58553510/cant-get-certs-working-with-cert-manager
comment
closed
kyprifog
username_0
issue