Skip to content

Kuma validation init container was not able to re-connect once application containers restarts #13401

Open
@adarsh-padhi

Description

@adarsh-padhi

Kuma Version

2.9.4

Describe the bug

Hii team ,

Recently One of the DPPs faced issue , where the kuma-validation init-container was not able to come up resulting the application pod in hung state

Upon Investigating we found out that the pod's suddenly restarted & post that kuma-validation init container was continuously restarting , it was only with that pod & rest 2 replicas were running fine at the same time ,
Once we restarted the pod , it started working

need to know what caused the issue , we even checked the kuma-cni pods , we didn't found anything.

Kuma-cni Pods logs

Image

kuma-validation logs

Image

To Reproduce

No response

Expected behavior

No response

Additional context (optional)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions