search

kumahq / kuma

🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.
https://kuma.io/install
Apache License 2.0
3.67k stars 333 forks source link

kuma + codezero #3099

Closed mayaaravotwm closed 2 years ago

mayaaravotwm commented 3 years ago

hello, we have kong ingress as our ingress controller on our aws eks cluster, and kuma as our service mesh. whenever we intercept or teleport a deployment using codezero , we can't access the service from outside, only from the inside. so the internal routes work well but the external don't work. it is relevant to both the original service and the intercepted one as well. we have kuma sidecar added to each pod in the namespace.

what can we do?

kuma 1.2.0 @c6o/cli/1.1.1 darwin-x64 node-v14.17.3

github-actions[bot] commented 2 years ago

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

lahabana commented 2 years ago

Could you maybe describe what the setup looks like. When you talk about inside/outside are you talking inside k8s or inside Kuma? Do you know how CodeZero works? Is it very similar to kubectl port-forward?

lahabana commented 2 years ago

Considering the generality and lack of context on this ticket. I'd like us to review this at triage and consider closing it.

jakubdyszkiewicz commented 2 years ago

Triage: Closing for now. Feel free to reopen this if you can provide more information