Enable mTLS Across the Service Mesh

Turn on strict mTLS in the mesh so all inter-service traffic is encrypted and a pod on a compromised node cannot sniff calls.

~25 minkubernetesmtlsservice-mesh

Task

Configure istioctl install --set values.global.mtls.mode=strict so the cluster enforces the policy at admission time instead of relying on manual review.

When to use this

A developer deploys a pod without istioctl install --set values.global.mtls.mode=strict and it disrupts a node, causing evictions on a production cluster.

Prerequisites

A Kubernetes cluster with kubectl access
Cluster admin or namespace edit RBAC

Steps

1. Configure istioctl install --set values.global.mtls.mode=strict in the project configuration file with the recommended defaults.

istioctl install --set values.global.mtls.mode=strict

Expected output: The configuration is accepted and istioctl install --set values.global.mtls.mode=strict runs without errors on the first invocation.

2. Run the check locally to verify istioctl install --set values.global.mtls.mode=strict produces the expected result before pushing.

pnpm test

Expected output: Local run matches CI behavior; no surprises after push.

3. Add the gate to the CI pipeline so istioctl install --set values.global.mtls.mode=strict blocks merge on failure.

- name: Run add service mesh mtls
  run: pnpm test

Expected output: Pull requests with failing istioctl install --set values.global.mtls.mode=strict are blocked from merging.

Troubleshooting

Problem

The check passes locally but fails in CI

Solution

Pin dependency versions and the runtime to match CI exactly; reproduce with the same Docker image or act.

Problem

Configuration is rejected with a schema error

Solution

Check the tool version matches the config schema; older versions may not support newer fields.

Limitations

The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
Configuration drift is possible if someone edits settings outside version control.

Enforce at admission

Start by measuring the problem. Turn on strict mTLS in the mesh so all inter-service traffic is encrypted and a pod on a compromised node cannot sniff calls. The most common mistake is adding the gate without first confirming it catches the issue you care about. Run istioctl install –set values.global.mtls.mode=strict against the current codebase and inspect the output before wiring it into CI.

istioctl install --set values.global.mtls.mode=strict

Verify the policy

Once the gate is in place, make failures actionable. A failing istioctl install –set values.global.mtls.mode=strict should point to the exact file and line, not a generic error. Pin the tool version in the lockfile so a upstream release does not silently change behavior. Review the gate output in every pull request just like a test result.