Zero-trust between services.
An Istio AuthorizationPolicy lets you say "only the
service-account 'frontend' in namespace 'shop' may call the
'payments' service on POST /charge". The benefit vs network policies is:
A) NetworkPolicies use IPs (which churn in K8s); AuthorizationPolicies
use cryptographic identity (mTLS SPIFFE IDs) and HTTP-level rules
(path, method, JWT claims).
B) AuthorizationPolicies are slower.
C) They replace RBAC for kubectl access.
D) They only work on UDP.Sign in to save your code and track progress across devices.
