zalando skipper east-to-west communication (internal service to service) cross namespace

12/9/2019

Wondering if anyone who has experience with implementing zalando skipper east-to-west communication. I want to know if it's possible to do service to service routing, specially for cross namespace service? I tried without east-to-west and found that when using external service pointing to a different service in another namespace (e.g. svcname.diff-namespace.svc.cluster.local), it resolves to nothing. Basically I need to do site routing based on path (e.g. www.domain.com goes to backend1, www.domain.com/user goes to backend2; backend1 and backend2 are in different namespaces). I am already using aws-ingress-controller from zalando using 1 ALB. So far, I use external frontend to do this, but want to find out solution that is implemented at kubernetes. Any hints? Thank you.

-- Lito Kusnadi
kubernetes
kubernetes-ingress
kubernetes-service
skipper

0 Answers