In a multi-primary deployment, you want to ensure that traffic between clusters is encrypted via mTLS. Which resource must be configured on both clusters?
Trap 1: A ServiceEntry with 'resolution: DNS'.
ServiceEntry handles routing and discovery, not identity and trust.
Trap 2: An AuthorizationPolicy allowing all traffic.
This affects authorization, not the trust domain required for mTLS encryption.
Trap 3: An EgressGateway with TLS origination.
EgressGateway is for traffic exiting the mesh to external services, not for inter-cluster traffic.
- A
A shared 'cacerts' secret containing the root CA certificate.
All clusters must trust the same root CA to validate identities across cluster boundaries.
- B
A ServiceEntry with 'resolution: DNS'.
Why wrong: ServiceEntry handles routing and discovery, not identity and trust.
- C
An AuthorizationPolicy allowing all traffic.
Why wrong: This affects authorization, not the trust domain required for mTLS encryption.
- D
An EgressGateway with TLS origination.
Why wrong: EgressGateway is for traffic exiting the mesh to external services, not for inter-cluster traffic.