never_inline parent
Can someone enlighten me on this: if Authorization policies (which pods can communicate with which services) was built in kube-proxy, wouldn't it solve the use case for a large percent of service mesh deployments?
Kube proxy works configuring ip tables (oversimplified) and its scope is limitted to l4. It doesn't operate at L7.
Isn't that what k8s network policies do?
The support varies by CNI so I wouldn't call it "built-in".
But yeah I forgot this existed.
Isn't that what k8s network policies do