search

Kong / kubernetes-ingress-controller

:gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
https://docs.konghq.com/kubernetes-ingress-controller/
Apache License 2.0
2.22k stars 594 forks source link

New Topic: Securing the KIC-kong #4949

Open Rajakavitha1 opened 1 year ago

Rajakavitha1 commented 1 year ago

Is there an existing issue for this?

Problem Statement

As a user, I'd like to know how to secure KIC-Kong communication with mTLS when using Gateway Discovery

Proposed Solution

No response

Additional information

No response

Acceptance Criteria

mheap commented 1 year ago

https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/using-gateway-discovery/ mentions the following:

As Kong Ingress Controller and Kong Gateway deployments are separate, you should enable TLS client verification for the Admin API service so that no one from inside the cluster can access it without a valid certificate. This can be done by setting ingressController.adminApi.tls.client.enabled option in the Helm chart to true. It will create a CA certificate and a CA-signed certificate for the client, and respective Kubernetes TLS Secrets for both.

I'll test these instructions first