![We know that POD’s can contain multiple containers. Containers within the POD will share the same network namespace (i.e means containers within the POD’s will share the same IP & can communicate with each other through localhost address) & shared storage.⠀
⠀
By Default, Each container runs in unique isolated Process Namespace.you can’t exchange message across the container through IPC (inter-process communication)⠀
⠀
With 1.17 release, Now the container within the POD can share the Process Namespace as well. By enabling the shareProcessNamespace: true in the Pod Spec.⠀
⠀
Let's create a Pod with shared Process Namespace [...]⠀
⠀
Use the link 🔗 in our bio to discover this story and more.⠀
⠀
#kubernetes #pods #share-process-namespace](http://scontent-lax3-1.cdninstagram.com/v/t51.2885-15/e15/s320x320/81142973_180963849955977_8513677892093429989_n.jpg?_nc_ht=scontent-lax3-1.cdninstagram.com&_nc_cat=109&_nc_ohc=VrEDJ6S_UzQAX_p362c&oh=e7b46010edea094c9bc03d1a2791cd3d&oe=5EC0F00B)
How to deploy a PostgreSQL Cluster on Kubernetes + OpenEBS
2.6K Views November 1, 2017 2 Comments
Why Postgres on Kubernetes? Well, the answer is in the question. If you are already running Kubernetes on some form of cloud, you understand the ease-of-use, scalability and monitoring…