Abstract: Techniques are presented herein for providing a persistent external Internet Protocol (IP) address for extra-cluster services. One example involves initiating, in a cluster, a first pod with a label that identifies a service. The first pod is configured to provide the service to one or more network entities outside the cluster. The first pod is assigned an IP address configured for communicating outside the cluster. A mapping of the service to the IP address is stored. In response to a determination that the service has been disrupted, a second pod is initiated in the cluster with the label that identifies the service. The second pod is configured to provide the service to the one or more network entities outside the cluster. Based on the mapping and the label that identifies the service, the IP address is assigned to the second pod.

Abstract: Techniques are presented herein for providing a persistent external Internet Protocol (IP) address for extra-cluster services. One example involves initiating, in a cluster, a first pod with a label that identifies a service. The first pod is configured to provide the service to one or more network entities outside the cluster. The first pod is assigned an IP address configured for communicating outside the cluster. A mapping of the service to the IP address is stored. In response to a determination that the service has been disrupted, a second pod is initiated in the cluster with the label that identifies the service. The second pod is configured to provide the service to the one or more network entities outside the cluster. Based on the mapping and the label that identifies the service, the IP address is assigned to the second pod.

Abstract: Techniques are presented herein for providing a persistent external Internet Protocol (IP) address for extra-cluster services. One example involves initiating, in a cluster, a first pod with a label that identifies a service. The first pod is configured to provide the service to one or more network entities outside the cluster. The first pod is assigned an IP address configured for communicating outside the cluster. A mapping of the service to the IP address is stored. In response to a determination that the service has been disrupted, a second pod is initiated in the cluster with the label that identifies the service. The second pod is configured to provide the service to the one or more network entities outside the cluster. Based on the mapping and the label that identifies the service, the IP address is assigned to the second pod.

Abstract: Techniques are provided for detecting and identifying host devices in a network. At a switch device, a packet is received from a server that is interfaced with a switch device and is configured to host a virtual machine that is a source of the packet. A Media Access Control (MAC) address or an Internet Protocol (IP) address is identified. The MAC address and IP address are associated with the virtual machine. In response to identifying the MAC or IP addresses, the switch device determines whether a binding between the IP and MAC addresses of the virtual machine is present in a database of addresses accessible by the switch device. If the association is not present, based on the fields obtained from the packet header, a request message is sent to the virtual machine to resolve the association between the IP address and the MAC address of the virtual machine.

Abstract: Techniques are provided for detecting and identifying host devices in a network. At a switch device, a packet is received from a server that is interfaced with a switch device and is configured to host a virtual machine that is a source of the packet. A Media Access Control (MAC) address or an Internet Protocol (IP) address is identified. The MAC address and IP address are associated with the virtual machine. In response to identifying the MAC or IP addresses, the switch device determines whether a binding between the IP and MAC addresses of the virtual machine is present in a database of addresses accessible by the switch device. If the association is not present, based on the fields obtained from the packet header, a request message is sent to the virtual machine to resolve the association between the IP address and the MAC address of the virtual machine.