我的书签
添加书签
移除书签Mutual TLS over HTTPS
This task shows how mutual TLS works with HTTPS services. It includes:
Deploying an HTTPS service without Istio sidecar
Deploying an HTTPS service with Istio with mutual TLS disabled
Deploying an HTTPS service with mutual TLS enabled. For each deployment, connect to this service and verify it works.
When the Istio sidecar is deployed with an HTTPS service, the proxy automatically downgradesfrom L7 to L4 (no matter mutual TLS is enabled or not), which means it does not terminate theoriginal HTTPS traffic. And this is the reason Istio can work on HTTPS services.
Before you begin
Set up Istio by following the instructions in thequick start.Note that default mutual TLS authentication should be disabled when installing Istio using the demo profile.
The demo is also assumed to be running in a namespace where automatic sidecar injection isdisabled, and Istio sidecars are instead manually injected with istioctl.
Generate certificates and configmap
The following examples consider an NGINX service pod which can encrypt traffic using HTTPS.Before beginning, generate the TLS certificate and key that this service will use.
You need to have openssl installed to run these commands:
$ openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /tmp/nginx.key -out /tmp/nginx.crt -subj "/CN=my-nginx/O=my-nginx"$ kubectl create secret tls nginxsecret --key /tmp/nginx.key --cert /tmp/nginx.crtsecret "nginxsecret" created
Create a configmap used for the HTTPS service
$ kubectl create configmap nginxconfigmap --from-file=samples/https/default.confconfigmap "nginxconfigmap" created
Deploy an HTTPS service without the Istio sidecar
This section creates a NGINX-based HTTPS service.
$ kubectl apply -f @samples/https/nginx-app.yaml@service "my-nginx" createdreplicationcontroller "my-nginx" created
Then, create another pod to call this service.
$ kubectl apply -f <(istioctl kube-inject -f @samples/sleep/sleep.yaml@)
Get the pods
$ kubectl get podNAME READY STATUS RESTARTS AGEmy-nginx-jwwck 1/1 Running 0 1hsleep-847544bbfc-d27jg 2/2 Running 0 18h
Ssh into the istio-proxy container of sleep pod.
$ kubectl exec -it $(kubectl get pod -l app=sleep -o jsonpath={.items..metadata.name}) -c istio-proxy /bin/bash
Call my-nginx
$ curl https://my-nginx -k...<h1>Welcome to nginx!</h1>...
You can actually combine the above three command into one:
$ kubectl exec $(kubectl get pod -l app=sleep -o jsonpath={.items..metadata.name}) -c istio-proxy -- curl https://my-nginx -k...<h1>Welcome to nginx!</h1>...
Create an HTTPS service with the Istio sidecar and mutual TLS disabled
In “Before you begin” section, the Istio control plane is deployed with mutual TLSdisabled. So you only need to redeploy the NGINX HTTPS service with sidecar.
Delete the HTTPS service.
$ kubectl delete -f @samples/https/nginx-app.yaml@
Deploy it with a sidecar
$ kubectl apply -f <(istioctl kube-inject -f @samples/https/nginx-app.yaml@)
Make sure the pod is up and running
$ kubectl get podNAME READY STATUS RESTARTS AGEmy-nginx-6svcc 2/2 Running 0 1hsleep-847544bbfc-d27jg 2/2 Running 0 18h
And run
$ kubectl exec $(kubectl get pod -l app=sleep -o jsonpath={.items..metadata.name}) -c sleep -- curl https://my-nginx -k...<h1>Welcome to nginx!</h1>...
If you run from the istio-proxy container, it should work as well:
$ kubectl exec $(kubectl get pod -l app=sleep -o jsonpath={.items..metadata.name}) -c istio-proxy -- curl https://my-nginx -k...<h1>Welcome to nginx!</h1>...
This example is borrowed from Kubernetes examples.
Create an HTTPS service with Istio sidecar with mutual TLS enabled
You need to deploy Istio control plane with mutual TLS enabled. If you have the Istiocontrol plane with mutual TLS disabled installed, please delete it. For example, ifyou followed the quick start:
$ istioctl manifest generate --set profile=demo | kubectl delete -f -
And wait for everything to have been deleted, i.e., there is no pod in the control plane namespace (istio-system):
$ kubectl get pod -n istio-systemNo resources found.
Install Istio with the strict mutual TLS mode enabled:
$ istioctl manifest apply --set profile=demo,values.global.controlPlaneSecurityEnabled=true,values.global.mtls.enabled=true
Make sure everything is up and running:
$ kubectl get po -n istio-systemNAME READY STATUS RESTARTS AGEgrafana-6f6dff9986-r6xnq 1/1 Running 0 23histio-citadel-599f7cbd46-85mtq 1/1 Running 0 1histio-cleanup-old-ca-mcq94 0/1 Completed 0 23histio-egressgateway-78dd788b6d-jfcq5 1/1 Running 0 23histio-ingressgateway-7dd84b68d6-dxf28 1/1 Running 0 23histio-mixer-post-install-g8n9d 0/1 Completed 0 23histio-pilot-d5bbc5c59-6lws4 2/2 Running 0 23histio-policy-64595c6fff-svs6v 2/2 Running 0 23histio-sidecar-injector-645c89bc64-h2dnx 1/1 Running 0 23histio-statsd-prom-bridge-949999c4c-mv8qt 1/1 Running 0 23histio-telemetry-cfb674b6c-rgdhb 2/2 Running 0 23histio-tracing-754cdfd695-wqwr4 1/1 Running 0 23hprometheus-86cb6dd77c-ntw88 1/1 Running 0 23h
Then redeploy the HTTPS service and sleep service
$ kubectl delete -f <(istioctl kube-inject -f @samples/sleep/sleep.yaml@)$ kubectl apply -f <(istioctl kube-inject -f @samples/sleep/sleep.yaml@)$ kubectl delete -f <(istioctl kube-inject -f @samples/https/nginx-app.yaml@)$ kubectl apply -f <(istioctl kube-inject -f @samples/https/nginx-app.yaml@)
Make sure the pod is up and running
$ kubectl get podNAME READY STATUS RESTARTS AGEmy-nginx-9dvet 2/2 Running 0 1hsleep-77f457bfdd-hdknx 2/2 Running 0 18h
And run
$ kubectl exec $(kubectl get pod -l app=sleep -o jsonpath={.items..metadata.name}) -c sleep -- curl https://my-nginx -k...<h1>Welcome to nginx!</h1>...
The reason is that for the workflow “sleep -> sleep-proxy -> nginx-proxy -> nginx”,the whole flow is L7 traffic, and there is a L4 mutual TLS encryption between sleep-proxyand nginx-proxy. In this case, everything works fine.
However, if you run this command from the istio-proxy container, it will not work:
$ kubectl exec $(kubectl get pod -l app=sleep -o jsonpath={.items..metadata.name}) -c istio-proxy -- curl https://my-nginx -kcurl: (35) gnutls_handshake() failed: Handshake failedcommand terminated with exit code 35
The reason is that for the workflow “sleep-proxy -> nginx-proxy -> nginx”,nginx-proxy is expected mutual TLS traffic from sleep-proxy. In the command above,sleep-proxy does not provide client cert. As a result, it won’t work. Moreover,even sleep-proxy provides client cert in above command, it won’t work eithersince the traffic will be downgraded to http from nginx-proxy to nginx.
Cleanup
$ kubectl delete -f @samples/sleep/sleep.yaml@$ kubectl delete -f @samples/https/nginx-app.yaml@$ kubectl delete configmap nginxconfigmap$ kubectl delete secret nginxsecret
See also
Shows you how to verify and test Istio's automatic mutual TLS authentication.
Provision and manage DNS certificates in Istio.
Introducing the Istio v1beta1 Authorization Policy
Introduction, motivation and design principles for the Istio v1beta1 Authorization Policy.
A more secure way to manage Istio webhooks.
Istio as a Proxy for External Services
Configure Istio ingress gateway to act as a proxy for external services.
Multi-Mesh Deployments for Isolation and Boundary Protection
Deploy environments that require isolation into separate meshes and enable inter-mesh communication by mesh federation.
