662794bded
By default pods in Kubernetes can connect to each other. However in Qinling, each pod should be independent acting as a worker of a function or running an execution of a function. Disabling the inter-pods traffic in the namespace used by Qinling would ensure the isolation of each pod. This commit leverages the NetworkPolicy in Kubernetes[1] to isolate the pods. So a network solution which supports NetworkPolicy (for example, cailco) for Kubernetes must be used or there will be no effect. [1] https://kubernetes.io/docs/concepts/services-networking/network-policies/ Story: 2001585 Task: 6534 Change-Id: I368323410e92cc23c9a7b50e4936c7070cd57ef7 |
||
---|---|---|
.. | ||
.placeholder | ||
enable-mutable-configuration-a0527660fa58532c.yaml | ||
function-versioning-6e23fc021c2a7c7e.yaml | ||
get-runtime-pool-information-440351400ad7f0b8.yaml | ||
isolate-k8s-pods-617fec5dc5fbd2d8.yaml | ||
qinling-k8s-apiserver-certs-1651e26de5ca001c.yaml | ||
resources-customized-5f5382d40e375dc1.yaml |