Security Best Practices
This section provides some deployment guidelines to help keep a service mesh secure.
Use namespaces for isolation
If there are multiple service operators (a.k.a. SREs)
deploying different services in a medium- or large-size cluster, we recommend creating a separate
Kubernetes namespace for each SRE team to isolate their access.
For example, you can create a
team1-ns namespace for
team2-ns namespace for
that both teams cannot access each other’s services.
Let us consider a three-tier application with three services:
datastore. The photo SRE team manages the
photo-backend services while the datastore SRE team
datastore service. The
photo-frontend service can access
photo-backend, and the
photo-backend service can access
photo-frontend service cannot access
In this scenario, a cluster administrator creates three namespaces:
datastore-ns. The administrator has
access to all namespaces and each team only has access to its own namespace.
The photo SRE team creates two service accounts to run
photo-backend respectively in the
photo-ns namespace. The datastore SRE
team creates one service account to run the
datastore service in the
datastore-ns namespace. Moreover, we need to enforce the service access
control in Istio Mixer such that
photo-frontend cannot access datastore.
In this setup, Kubernetes can isolate the operator privileges on managing the services. Istio manages certificates and keys in all namespaces and enforces different access control rules to the services.