Abstract: Techniques are described for implementing a container environment where each pod within the container environment is provided with a unique IP address and a virtual communication device such as an IPvlan device. Communications from source pods are directly routed to destination pods within the container environment by one or more virtualized network interface cards (VNICs) utilizing the unique IP addresses of the destination pods, without the need for bridging and encapsulation. This reduces a size of data being transmitted and also eliminates a compute cost necessary to perform encapsulation of data during transmission.

Abstract: In some implementations, the techniques may include receiving a request to launch a first instance in a customer partition. The request can identify one or more of a cluster and an instance image. In addition, the techniques may include launching the first instance on a server in the customer partition using the instance image identified by the request. The techniques may include receiving a request to authenticate the first instance. Moreover, the techniques may include in response to a determination that the first instance is authentic: adding the first instance to the cluster identified in the request.

Abstract: Techniques are described for implementing a container environment where each pod within the container environment is provided with a unique IP address and a virtual communication device such as an IPvlan device. Communications from source pods are directly routed to destination pods within the container environment by one or more virtualized network interface cards (VNICs) utilizing the unique IP addresses of the destination pods, without the need for bridging and encapsulation. This reduces a size of data being transmitted and also eliminates a compute cost necessary to perform encapsulation of data during transmission.