proposal: provide istio mTLS resources
See original GitHub issueCurrently the manifests in release/istio-manifests.yaml
are designed for PERMISSIVE
mTLS authentication.
If the user sets mTLS is set to STRICT
for either the Hipstershop service(s), globally, or for the namespace in which Hipstershop is , frontend
(and potentially other services) will not start up due to the Liveness/Readiness probes.
I propose we create Istio manifests for both PERMISSIVE and STRICT mTLS – and instruct users to use the PERMISSIVE manifests by default.
See Bookinfo for an example of how we might separate out the manifests.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Security Best Practices - Istio
Istio security features provide strong identity, powerful policy, transparent TLS encryption, and authentication, authorization and audit (AAA) tools to ...
Read more >How to Secure & Scale Istio Mtls with Enterprise PKI - Keyfactor
If you're making the move to Istio service mesh, there are a lot of things you'll need to consider – security being number...
Read more >Securing Istio workloads with mTLS using cert-manager - Venafi
As Kubernetes adoption grows, there is now increased interest in service mesh to securely connect workloads, as well as provide dynamic ...
Read more >Anthos Service Mesh by example: mTLS - Google Cloud
With auto mTLS, a client sidecar proxy automatically detects if the server has a sidecar. The client sidecar sends mTLS to workloads with...
Read more >Managing Policies and Security with Istio
Incrementally adopting Istio mutual TLS authentication across the service ... how long Google Cloud resources will be made available to you.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Readiness and liveness probes should now work with istio mTLS.
Will address in: https://github.com/GoogleCloudPlatform/microservices-demo/issues/211
For existing deployments, such as Istio on GKE, the way to rewrite probes is to modify the istio-sidecar-injector configmap to set rewriteAppHTTPProbe to true. The primary complication there is that this value appears to have been added in 1.1, and I assume you would like to allow 1.0.x deployments (such as Istio on GKE).
I will investigate the viability of this feature on releases back through whatever Istio on GKE is using.