title: Kubernetes Ingress Controller Fake Certificate on GKE for WSO2 API Management
body: <p><a href="https://i.stack.imgur.com/Fbhna.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Fbhna.png" alt="enter image description here" /></a></p>
  <p>I encourage an issue regarding setup the TLS Cert-Manager Controller on GKE for WSO2 API Management.</p>
  <hr />
  <p>I am using WSO2 product Docker images available from WSO2 Private Docker Registry, following the Helm Chart for the deployment of WSO2 API Manager with WSO2 API Manager Analytics on Github (<a href="https://github.com/wso2/kubernetes-apim/blob/master/advanced/am-pattern-1/README.md" rel="nofollow noreferrer">README</a>). And I successfully deployed the WSO2 API Manager with Nginx Ingress Controller (<a href="https://medium.com/bluekiri/deploy-a-nginx-ingress-and-a-certitificate-manager-controller-on-gke-using-helm-3-8e2802b979ec" rel="nofollow noreferrer">deploy-a-nginx-ingress-and-a-certitificate-manager-controller-on-gke</a>).</p>
  <hr />
  <p>I want to create a Kubernetes cluster on Google Cloud Platform using an Nginx Ingress Controller to integrate with a certificate manager to automate the process of issue and renew the required certificates.</p>
  <hr />
  <p>I easily replicate the TLS Cert-Manager Controller on GKE for HelloWorld example from the same medium tutorial (<a href="https://medium.com/bluekiri/deploy-a-nginx-ingress-and-a-certitificate-manager-controller-on-gke-using-helm-3-8e2802b979ec" rel="nofollow noreferrer">deploy-a-nginx-ingress-and-a-certitificate-manager-controller-on-gke</a>).</p>
  <p><a href="https://i.stack.imgur.com/PFLOs.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/PFLOs.jpg" alt="enter image description here" /></a></p>
  <p><strong>hello-app-ingress.yaml</strong></p>
  <pre><code>apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    annotations:
      cert-manager.io/issuer: letsencrypt-production
      kubectl.kubernetes.io/last-applied-configuration: |
        {&quot;apiVersion&quot;:&quot;networking.k8s.io/v1beta1&quot;,&quot;kind&quot;:&quot;Ingress&quot;,&quot;metadata&quot;:{&quot;annotations&quot;:{&quot;cert-manager.io/issuer&quot;:&quot;letsencrypt-production&quot;,&quot;kubernetes.io/ingress.class&quot;:&quot;nginx&quot;,&quot;nginx.ingress.kubernetes.io/ssl-redirect&quot;:&quot;true&quot;},&quot;name&quot;:&quot;hello-app-ingress&quot;,&quot;namespace&quot;:&quot;default&quot;},&quot;spec&quot;:{&quot;rules&quot;:[{&quot;host&quot;:&quot;test.japangly.xyz&quot;,&quot;http&quot;:{&quot;paths&quot;:[{&quot;backend&quot;:{&quot;serviceName&quot;:&quot;hello-app&quot;,&quot;servicePort&quot;:8080},&quot;path&quot;:&quot;/helloworld&quot;}]}}],&quot;tls&quot;:[{&quot;hosts&quot;:[&quot;test.japangly.xyz&quot;],&quot;secretName&quot;:&quot;test-japangly-xyz-tls&quot;}]}}
      kubernetes.io/ingress.class: nginx
      nginx.ingress.kubernetes.io/ssl-redirect: &quot;true&quot;
    creationTimestamp: &quot;2020-08-30T04:27:12Z&quot;
    generation: 3
    name: hello-app-ingress
    namespace: default
    resourceVersion: &quot;6478&quot;
    selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/hello-app-ingress
    uid: ea2d8b13-e9b6-4cb0-873d-76ed40253e4f
  spec:
    rules:
    - host: test.japangly.xyz
      http:
        paths:
        - backend:
            serviceName: hello-app
            servicePort: 8080
          path: /helloworld
    tls:
    - hosts:
      - test.japangly.xyz
      secretName: test-japangly-xyz-tls
  status:
    loadBalancer:
      ingress:
      - ip: 35.239.145.46
  </code></pre>
  <p>However, not working the WSO2 API Management, all I get is</p>
  <blockquote>
  <p>Kubernetes Ingress Controller Fake Certificate</p>
  </blockquote>
  <p><a href="https://i.stack.imgur.com/xx4d5.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/xx4d5.png" alt="enter image description here" /></a></p>
  <p><strong>wso2am-pattern-1-am-ingress.yaml</strong></p>
  <pre><code>apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    annotations:
      cert-manager.io/issuer: letsencrypt-production
      kubernetes.io/ingress.class: nginx
      meta.helm.sh/release-name: wso2am-pattern-1
      meta.helm.sh/release-namespace: wso2-apim
      nginx.ingress.kubernetes.io/affinity: cookie
      nginx.ingress.kubernetes.io/backend-protocol: HTTPS
      nginx.ingress.kubernetes.io/session-cookie-hash: sha1
      nginx.ingress.kubernetes.io/session-cookie-name: route
      nginx.ingress.kubernetes.io/ssl-redirect: &quot;true&quot;
    creationTimestamp: &quot;2020-08-30T04:41:10Z&quot;
    generation: 4
    labels:
      app.kubernetes.io/managed-by: Helm
    name: wso2am-pattern-1-am-ingress
    namespace: wso2-apim
    resourceVersion: &quot;88840&quot;
    selfLink: /apis/extensions/v1beta1/namespaces/wso2-apim/ingresses/wso2am-pattern-1-am-ingress
    uid: 58f4b549-a565-493b-9f9f-72ad76877819
  spec:
    rules:
    - host: am.japangly.xyz
      http:
        paths:
        - backend:
            serviceName: wso2am-pattern-1-am-service
            servicePort: 9443
          path: /
    tls:
    - hosts:
      - am.japangly.xyz
      secretName: am-japangly-xyz-tls
  status:
    loadBalancer:
      ingress:
      - ip: 35.239.145.46
  </code></pre>