Choose the best description of what a service mesh does in a Kubernetes environment.
Think about what helps microservices communicate securely and reliably inside Kubernetes.
A service mesh handles communication between microservices, adding features like load balancing, security (mTLS), and observability without changing application code.
What is the output when you run the following command to label a namespace for automatic Istio sidecar injection?
kubectl label namespace default istio-injection=enabled
Labeling a namespace adds a label; it does not create or delete namespaces.
The command adds the label 'istio-injection=enabled' to the existing 'default' namespace and confirms with 'namespace/default labeled'.
Which YAML snippet correctly enables mutual TLS (mTLS) for all services in the default namespace using Istio PeerAuthentication?
Look for the correct apiVersion and kind that configures mTLS mode strictly.
PeerAuthentication with apiVersion security.istio.io/v1beta1 and mtls mode STRICT enables mutual TLS for all workloads in the namespace.
You deployed two microservices in Kubernetes with Istio service mesh enabled. Service A cannot reach Service B. Which of the following is the most likely cause?
In a service mesh, communication depends on sidecar proxies intercepting traffic.
If Service B's pod lacks the Istio sidecar proxy, the mesh cannot route traffic to it, causing communication failure.
Which practice is considered best for securing communication between microservices in a service mesh?
Think about encryption and automated security features in service meshes.
Enabling mTLS with strict mode ensures encrypted, authenticated communication. Regular certificate rotation maintains security.