Scan the pods in the current node to find those that have been injected by linkerd, and whose linkerd-network-validator container has failed, and proceed to evict them so they can restart and rety re-acquiring a proper network config

Usage:

Options:
      --log-level <LOG_LEVEL>
          [env: LINKERD_CNI_REPAIR_CONTROLLER_LOG_LEVEL=] [default: linkerd_cni_repair_controller=info,warn]
      --log-format <LOG_FORMAT>
          [env: LINKERD_CNI_REPAIR_CONTROLLER_LOG_FORMAT=] [default: plain]
      --node-name <NODE_NAME>
          [env: LINKERD_CNI_REPAIR_CONTROLLER_NODE_NAME=]
      --controller-pod-name <CONTROLLER_POD_NAME>
          [env: LINKERD_CNI_REPAIR_CONTROLLER_POD_NAME=]
      --cluster <CLUSTER>
          The name of the kubeconfig cluster to use
      --context <CONTEXT>
          The name of the kubeconfig context to use
      --user <USER>
          The name of the kubeconfig user to use
      --kubeconfig <KUBECONFIG>
          The path to the kubeconfig file to use
      --as <IMPERSONATE_USER>
          Username to impersonate for Kubernetes operations
      --as-group <IMPERSONATE_GROUP>
          Group to impersonate for Kubernetes operations
      --kube-api-response-headers-timeout <RESPONSE_HEADERS_TIMEOUT>
          The timeout for response headers from the Kubernetes API [default: 9s]
      --admin-addr <ADMIN_ADDR>
          The admin server's address [default: 0.0.0.0:8080]
  -h, --help
          Print help
  -V, --version
          Print version