To run a container in a Kubernetes environment, you should define a YAML manifest for the container and its resources2. YAML manifests are used to define Kubernetes objects, such as pods or services.These manifests describe the desired state of the system2.

In Juniper Cloud-Native Contrail Networking (CN2), isolated namespaces are used to isolate a pod from other pods without explicitly configuring a network policy3.Pods in an isolated namespace can only communicate with pods in the same namespace3.They cannot reach pods or services in other isolated or non-isolated namespaces3.

A CN2 controller communicates with CN2 vRouters using XMPP (Extensible Messaging and Presence Protocol) and with other CN2 controllers using BGP (Border Gateway Protocol). XMPP is used for control plane communication, while BGP is used for routing updates between controllers.

OS-level virtualization requires less duplication of hardware resources. This method allows multiple instances of an operating system or multiple different operating systems to run on a single physical server, sharing the same hardware resources. This results in more efficient use of hardware resources compared to other virtualization methods such as full virtualization or paravirtualization

Containers are lightweight because they don't need the extra load of a hypervisor, but run directly within the host machine's kernel1. This means they start up almost instantly and use less RAM.Images are constructed from layered filesystems and share common files, making disk usage and image downloads much more efficient1. Containers are isolated from each other and the host system.They have their own filesystem and networking, and can be constrained to not allow root access outside the container1.They run on top of a host operating system1.