istio: Istio-cni CrashLoopBackOff after restarting the pod

Is this the right place to submit this?

  • This is not a security vulnerability or a crashing bug
  • This is not a question about how to use Istio

Bug Description

Description We are encountering an issue with Istio Ambient Mode after restarting one of the istio-cni pods on a node. The following behavior occurs:

  1. Steps to Reproduce

    • Ambient Mode is enabled in the cluster.
    • The istio-cni instance on one of the nodes is restarted, then it comes up again.
    • After the restart, the existing pods on the node continue to work fine.
    • However, When a new pod is scheduled on that node, it fails to start with the following error:
  2. Consequences:

    • The istio-cni pod works fine after the restart, but once the new pod is scheduled, the istio-cni pod begins failing and keeps restarting. I have attached the logs .
    • This causes issues with the ztunnel pod on the same node.
    • The issue can only be resolved by draining the node and moving the pods to another node.

Expected Behavior: After restarting the istio-cni instance, existing pods should continue to work, and new pods should start successfully without requiring node drainage.

Logs istio-cni.txt

Version

>istioctl version
client version: 1.24.2
control plane version: 1.24.2
data plane version: 1.24.2 (5 proxies)

>kubectl version
Client Version: v1.31.1
Kustomize Version: v5.4.2
Server Version: v1.30.8-eks-2d5f260

Additional Information

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (8 by maintainers)

Most upvoted comments