<p>I'm trying to set up cert-manager for m kubernetes cluster in Digitalocean.</p>
<p>after installing cert-manager and it making sure the services are running I make my issuer:</p>
<p><code>staging-issuer</code>:</p>
<pre><code>apiVersion: cert-manager.io/v1alpha2
kind: ClusterIssuer
metadata:
 name: letsencrypt-staging
 namespace: cert-manager
spec:
 acme:
   # The ACME server URL
   server: https://acme-staging-v02.api.letsencrypt.org/directory
   # Email address used for ACME registration
   email: myemail@mail.com
   # Name of a secret used to store the ACME account private key
   privateKeySecretRef:
     name: letsencrypt-staging
   # Enable the HTTP-01 challenge provider
   solvers:
   - http01:
       ingress:
         class:  nginx
</code></pre>
<p>Then in my ingress I add it as follows:</p>
<pre><code>apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: isildur-ingress
  annotations:
    cert-manager.io/cluster-issuer: &quot;letsencrypt-staging&quot;
spec:
  tls:
    - hosts:
      - auth-svc.url.com
      - email-service.url.com
      secretName: name-secret-tls
  rules:
  - host: email-service.url.com
    http:
      paths:
      - backend:
          serviceName: email-service
          servicePort: 3000
  - host: auth-svc.url.com
    http:
      paths:
      - backend:
          serviceName: auth-svc
          servicePort: 3000
        
</code></pre>
<p>Getting output from my ingress with <code>kubectl describe ingress</code>:</p>
<pre><code>  Normal  CreateCertificate  58s                cert-manager              Successfully created Certificate &quot;name-secret-tls&quot;
</code></pre>
<p>But then when I try and get the cert with <code>kubectl get certificate</code>:
<code>No resources found in default namespace.</code> . Adding <code>--all-namespaces</code> doesn't show anything either.</p>

Gurkmeja101
<p>I found the issue.
Gitlab had installed their cert-manager and it was conflicting with the one I had installed manually.</p>
