Defines the standard format for public-key certificates used to give workloads strong identities and secure service-to-service communication. section 4.3.3
In a service mesh, certificates support:
- Workload identity: the certificate represents a service’s role within the cluster. section 4.3.3
- Secure protocols: X.509 certificates underpin TLS/SSL, including HTTPS. section 4.3.3
- Mutual TLS: issued certificates enable transport authentication and encrypted service communication without application-code changes. section 4.3.3
- Operational automation: Istio agents and istiod automate key and certificate issuance, distribution, and rotation. section 4.3.3
Certificate-authority configurations
Istio can use a self-signed root certificate by default, or an administrator-specified root certificate and key, including a delegated CA signing certificate and key. Existing enterprise CA material is the common choice for enterprise deployments. section 4.3.3


