3 ms·
> They are running a single K8s cluster and expecting hard multi-tenancy guarantees? Maybe I missed something in the article but where are they expecting any h
by bilekas 2y ago
> They are running a single K8s cluster and expecting hard multi-tenancy guarantees?
Maybe I missed something in the article but where are they expecting any hard guarantees. If there is a model being trained for example (running arbitrary code) where does a multi K8 tenency play?
The main issue I see is all internal network communication was trusted once behind the proxy/firewall (Istio) but I probably just don't understand k8 clusters too well.
- robertlagrant 2y agoIstio is point to point between services. It's not a boundary in the sense you're thinking.
- bilekas 2y agoI will admit I don't know a lot about Kubernets at all, but as I see the Istio is supposed to be the proxy layer between services ? https://istio.io/latest/docs/ops/deployment/architecture/ https://istio.io/latest/docs/ops/deployment/architecture/ Being able to run as the Istio user (1337) renders the proxy itself moot right ?
- gbrayut 2y agoThere are a lot of other ways to bypass the Istio sidecar proxy, which is not designed to be a general egress boundary/firewall. See https://blog.howardjohn.info/posts/bypass-egress/ https://blog.howardjohn.info/posts/bypass-egress/