Open voidlily opened 1 day ago
Hi there, we have the same issue with the kong-dataplane deployment. No ContainerPatch on our side but the kong-dataplane already has another init container.
Could this be the issue fixed here already: https://github.com/kumahq/kuma/pull/11922 ?
Hi there, we have the same issue with the kong-dataplane deployment. No ContainerPatch on our side but the kong-dataplane already has another init container.
Do you also run in CNI mode? That might be the culprit and #11922 might be the fix after all
@voidlily or @slavogiez do you have a repro in a non risky environment?
If yes I'd love it if you could confirm that the preview artifact: 2.9.1-preview.v9beda2b29 indeed fixes you issues. Here's how to use these preview versions: https://kuma.io/docs/2.9.x/community/contribute-to-kuma/#testing-unreleased-versions
yeah looks like that fixed it, easy enough to test as well by changing global.image.tag
to that preview commit, thanks for publishing preview images on docker hub!
What happened?
I don't know exactly why this is happening yet, but it started happening to me in 2.9.0. Previously I was on 2.8.3 where I was not having issues with sidecar injection. This seems to happen to me regardless if I use injection labels on the namespace, or the Deployment.
kuma values.yaml
dp-resources patch referenced in the values.yaml
I tried on 2.9.0 disabling this patch as well but it didn't make a difference.