このページは、まだ日本語ではご利用いただけません。翻訳中です。
旧バージョンのドキュメントを参照しています。 最新のドキュメントはこちらをご参照ください。
mTLS
Configure the Kong Ingress Controller to verify client certificates using CA certificates and mtls-auth plugin for HTTPS requests.
Before you begin ensure that you have Installed Kong Ingress Controller with Gateway API support in your Kubernetes cluster and are able to connect to Kong. This guide requires Kong Gateway Enterprise.
Before you begin ensure that you have Installed Kong Ingress Controller with Gateway API support in your Kubernetes cluster and are able to connect to Kong. This guide requires Kong Gateway Enterprise.
Prerequisites
Install the Gateway APIs
-
Install the Gateway API CRDs before installing Kong Ingress Controller.
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.1.0/standard-install.yaml
-
Create a
Gateway
andGatewayClass
instance to use.echo " --- apiVersion: gateway.networking.k8s.io/v1 kind: GatewayClass metadata: name: kong annotations: konghq.com/gatewayclass-unmanaged: 'true' spec: controllerName: konghq.com/kic-gateway-controller --- apiVersion: gateway.networking.k8s.io/v1 kind: Gateway metadata: name: kong spec: gatewayClassName: kong listeners: - name: proxy port: 80 protocol: HTTP " | kubectl apply -f -
The results should look like this:
gatewayclass.gateway.networking.k8s.io/kong created gateway.gateway.networking.k8s.io/kong created
Install Kong
You can install Kong in your Kubernetes cluster using Helm.
-
Add the Kong Helm charts:
helm repo add kong https://charts.konghq.com helm repo update
-
Create a file named
license.json
containing your Kong Gateway Enterprise license and store it in a Kubernetes secret:kubectl create namespace kong kubectl create secret generic kong-enterprise-license --from-file=license=./license.json -n kong
-
Create a
values.yaml
file:gateway: image: repository: kong/kong-gateway env: LICENSE_DATA: valueFrom: secretKeyRef: name: kong-enterprise-license key: license
-
Install Kong Ingress Controller and Kong Gateway with Helm:
helm install kong kong/ingress -n kong --create-namespace --values ./values.yaml
Test connectivity to Kong
Kubernetes exposes the proxy through a Kubernetes service. Run the following commands to store the load balancer IP address in a variable named PROXY_IP
:
-
Populate
$PROXY_IP
for future commands:export PROXY_IP=$(kubectl get svc --namespace kong kong-gateway-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}') echo $PROXY_IP
-
Ensure that you can call the proxy IP:
curl -i $PROXY_IP
The results should look like this:
HTTP/1.1 404 Not Found Content-Type: application/json; charset=utf-8 Connection: keep-alive Content-Length: 48 X-Kong-Response-Latency: 0 Server: kong/3.0.0 {"message":"no Route matched with those values"}
-
Generate self-signed CA certificates using OpenSSL:
openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -sha256 -days 365 -nodes \ -subj "/C=US/ST=California/L=San Francisco/O=Kong/OU=Org/CN=www.example.com"
-
Add the generated certificates to Kong.
CA certificates in Kong are provisioned by creating a
Secret
resource in Kubernetes.CA certificate secrets must have the following properties:
- the
konghq.com/ca-cert: "true"
label applied. - a
cert
data property which contains a valid CA certificate in PEM format. - a
kubernetes.io/ingress.class
annotation whose value matches the value of the controller’s--ingress-class
argument. By default, that value iskong
. - an
id
data property which contains a random UUID.
Each CA certificate that you create needs a unique ID. Any random UUID should suffice here and it doesn’t have a security implication. You can use uuidgen (Linux, OS X) or New-Guid (Windows) to generate an ID.
$ kubectl create secret generic my-ca-cert --from-literal=id=cce8c384-721f-4f58-85dd-50834e3e733a --from-file=cert=./cert.pem $ kubectl label secret my-ca-cert 'konghq.com/ca-cert=true' $ kubectl annotate secret my-ca-cert 'kubernetes.io/ingress.class=kong'
The results should look like this:
secret/my-ca-cert created secret/my-ca-cert labeled secret/my-ca-cert annotated
- the
-
Configure
mtls-auth
KongPlugin resource which references the CA certificate. Make sure that the ID matches the ID provided in yourkubectl create secret
command:$ echo " apiVersion: configuration.konghq.com/v1 kind: KongPlugin metadata: name: mtls-auth config: ca_certificates: - cce8c384-721f-4f58-85dd-50834e3e733a skip_consumer_lookup: true revocation_check_mode: SKIP plugin: mtls-auth " | kubectl apply -f -
The results should look like this:
kongplugin.configuration.konghq.com/mtls-auth created
Deploy an echo service
To proxy requests, you need an upstream application to send a request to. Deploying this echo server provides a simple application that returns information about the Pod it’s running in:
kubectl apply -f https://docs.jp.konghq.com/assets/kubernetes-ingress-controller/examples/echo-service.yaml
The results should look like this:
service/echo created
deployment.apps/echo created
Add routing configuration
Create routing configuration to proxy /echo
requests to the echo server:
The results should look like this:
Test the routing rule:
curl -i $PROXY_IP/echo
The results should look like this:
HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
Content-Length: 140
Connection: keep-alive
Date: Fri, 21 Apr 2023 12:24:55 GMT
X-Kong-Upstream-Latency: 0
X-Kong-Proxy-Latency: 1
Via: kong/3.2.2
Welcome, you are connected to node docker-desktop.
Running on Pod echo-7f87468b8c-tzzv6.
In namespace default.
With IP address 10.1.0.237.
...
If everything is deployed correctly, you should see the above response. This verifies that Kong Gateway can correctly route traffic to an application running inside Kubernetes.
Add the konghq.com/plugin annotation
Test the configuration
-
Send a request to check Kong prompts you for client certificate.
$ curl -i -k https://$PROXY_IP/echo
The results should look like this:
HTTP/2 401 content-type: application/json; charset=utf-8 content-length: 50 x-kong-response-latency: 0 server: kong/2.0.4.0-enterprise-k8s {"message":"No required TLS certificate was sent"}
As you can see, Kong is restricting the request because it doesn’t have the necessary authentication information.
Two things to note here:
-
-k
is used because Kong is set up to serve a self-signed certificate by default. For full mutual authentication in production use cases, you must configure Kong to serve a certificate that is signed by a trusted CA. - For some deployments
$PROXY_IP
might contain a port that points tohttp
port of Kong. In others, it might happen that it contains a DNS name instead of an IP address. If needed, update the command to send anhttps
request to thehttps
port of Kong or the load balancer in front of it.
-
-
Use the key and certificate to authenticate against Kong and use the service:
$ curl --key key.pem --cert cert.pem https://$PROXY_IP/echo -k -I
The results should look like this:
HTTP/2 200 content-type: text/plain; charset=UTF-8 server: echoserver x-kong-upstream-latency: 1 x-kong-proxy-latency: 1 via: kong/2.0.4.0-enterprise-k8s