istio: istio-cni: failed to remove pod from mesh
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
Namespaces previously added to ambient mesh are not deleted
After removing the label (istio.io/dataplane-mode) from the tools namespace:
kubectl label ns tools istio.io/dataplane-mode-
the tools namespace continues to be in the ambient mesh:
./istioctl ztunnel-config workload
istio-cni logs:
Version
control plane version: 1.24.0
k8s: v1.30.4
CNI Plugin: cilium v1.16.3
Additional Information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 37 (30 by maintainers)
@ppalucki I suspect that the error you have in the logs about inpod rules not being deleted correctly should be addressed by my commit, that error led to an early exit in the RemovePodFromMesh() when certain iptables cfgs are used.
I noticed the same problem while working on the test cases for the idempotency/reconciliation PR so I tried to fix it. From the description of my PR:
On the other end, I cannot say for sure why sometimes you experienced the issue and sometimes you did not as I’m not well versed in the cni-agent logic.
If it’s feasible to have a smaller fix for the patch only id love to do it. Unfortunately I don’t have any ideas though
On Thu, Nov 14, 2024, 1:17 PM Leonardo Sarra @.***> wrote:
Yeah https://gitlab.com/apparmor/apparmor/-/wikis/TechnicalDoc_Proc_and_ptrace#apparmor-3-with-ptrace-rules implies that a bit.
On slack someone said privileged=true fixed it
On Mon, Nov 11, 2024, 10:29 AM Ben Leggett @.***> wrote: