Hrm, we've had a plan for a while, so whoever told you that may have been misinformed (sorry about that, not everyone always catches up). https://github.com/op

Hrm, we've had a plan for a while, so whoever told you that may have been misinformed (sorry about that, not everyone always catches up). https://github.com/openshift/origin/blob/master/pkg/cmd/infra/router/router.go#L78 https://github.com/openshift/origin/blob/master/pkg/cmd/infr... Is in 3.6, and other improvements will continue to be added. The one downside is that you have to grant the router proxies access to secrets, which means if someone compromises your edge ingress controller they can root your cluster unless you are very careful about only giving the routers access to exactly the secrets they need. That's partially why Routes contain their own secrets, so that you can't accidentally expose yourself to a cluster root. This sort of stuff is the details the OpenShift team spends most of its time on. Kube will eventually get most of this. But most people are running single tenant Kube clusters and so in Kube we spend more time focusing on making that work just right. It's pretty difficult to build a fully multitenant Kube setup without making choices that we're just not ready to do in Kube yet.