Open bharath-avesha opened 5 months ago
Can i work on this? please assign it to me if no one is working on it.
sure @kon3m. will assign it to you.
I followed the above steps but unfortunately was not able to reproduce the issue using KinD , is this issue reproducible in KinD @bharath-avesha
@kon3m can you please check if the nsm init and sidecar containers were injected into the pods in the bookinfo namespace? Those containers have to talk to the nsmgr control plane over tcp on port 5000. If the peer authentication is STRICT, istio sidecar in the bookinfo pod will try to enforce mtls on port 5000 and that will cause a failure because there is no istio sidecar in the nsmgr pods.
@bharath-avesha yes they are injected into the pods and the pods are in the running state without any restarts. Please let me know if i am doing anything wrong while trying to reproduce this bug.
Attaching the output of k get pod
π Description
Application pods in the bookinfo namespace connected to a slice go into a crashloop when using istio mtls peer authentication in STRICT mode.
π Reproduction steps
π Expected behavior
The app pods should not crash.
π Actual Behavior
The app pods go into a crash loop.
π Relevant log output
No response
Version
No response
π₯οΈ What operating system are you seeing the problem on?
No response
β Proposed Solution
No response
π Have you spent some time to check if this issue has been raised before?
Code of Conduct