KongIngress in different namespace

Hi there,

we are currently setup a Kong Gateway within our Kubernetes cluster.
If we create a KongIngress resource outside of our Ingress resource namespace we won’t be able to utilize it. Is there any workaround?
Also I don’t really understand the why we should use a KongIngress as long as we can use annotation within our Ingress resource.

kind: Ingress
metadata:
  name: kong-ingress-test
  namespace: dev
  annotations:
    kubernetes.io/tls-acme: "true"
    cert-manager.io/cluster-issuer: letsencrypt
    kubernetes.io/ingress.class: "kong"
    konghq.com/override: "kong-ingress-redirect-strip"
spec:
  tls:
  - secretName: domain.domain
    hosts:
      - domain.domain
  rules:
  - http:
      paths:
      - path: /patients
        backend:
          serviceName: patient-service-dev
          servicePort: 8080
apiVersion: configuration.konghq.com/v1
kind: KongIngress
metadata:
  name: kong-ingress-redirect-strip
  namespace: kong
route:
  https_redirect_status_code: 302
  strip_path: true
  protocols:
  - https

different namespace ?

No

Not all properties of KongIngress are exposed as annotations.


© 2019 Kong Inc.    Terms  •  Privacy  •  FAQ