linkerd2/cli
Steve Jenson 309e8d1210
Validate CNI configurations during pod startup (#9678)
When users use CNI, we want to ensure that network rewriting inside the pod is setup before allowing linkerd to start. When rewriting isn't happening, we want to exit with a clear error message and enough information in the container log for the administrator to either file a bug report with us or fix their configuration.

This change adds a validator initContainer to all injected workloads, when linkerd is installed with "cniEnabled=false". The validator replaces the noop init container, and will prevent pods from starting up if iptables is not configured.

Part of #8120

Signed-off-by: Steve Jenson <stevej@buoyant.io>
2022-10-26 11:14:45 +01:00
..
cmd Validate CNI configurations during pod startup (#9678) 2022-10-26 11:14:45 +01:00
flag Introduce LINKERD_DOCKER_REGISTRY and flexibilize CI workflows (#6782) 2021-09-01 13:39:05 -05:00
table Add linkerd viz authz command (#6875) 2021-09-21 09:36:05 -07:00
Dockerfile Update Go to 1.18 (#9019) 2022-07-27 16:10:39 -07:00
main.go Add `gosec` and `errcheck` lints (#7954) 2022-03-03 10:09:51 -07:00