NSX Container Plugin (NCP) provides integration between NSX-T Data Center and container orchestrators such as Kubernetes, as well as integration between NSX-T Data Center and container-based PaaS (platform as a service) products such as OpenShift and Pivotal Cloud Foundry.
The main component of NCP runs in a container and communicates with NSX Manager and with the Kubernetes control plane. NCP monitors changes to containers and other resources and manages networking resources such as logical ports, switches, routers, and security groups for the containers by calling the NSX API.
The NSX CNI plug-in runs on each Kubernetes node. It monitors container life cycle events, connects a container interface to the guest vSwitch, and programs the guest vSwitch to tag and forward container traffic between the container interfaces and the VNIC.
NSX Container Plugin (NCP) functionalities:
Automatically creates an NSX-T logical topology for a Kubernetes cluster, and creates a separate logical network for each Kubernetes namespace.
Connects Kubernetes pods to the logical network, and allocates IP and MAC addresses.
Supports network address translation (NAT) and allocates a separate SNAT IP for each Kubernetes namespace.
What’s New in NSX Container Plugin (NCP) 2.4?
- NCP Deployment support for Kubernetes.
- NCP HA for Kubernetes
- Error handling mechanism for NCP (Expose NSX backend failure to PaaS cluster)
- Support loadBalancerIP for service type LB
- Ability to specify ClientIP session affinity per LB type service
- NCP will exit if if fails to connect to PCF or Kubernetes server
- Make the foundation name optional for PAS
- Package ovs rpm for RHEL7.6
- SSL passthrough for OpenShift route
- Named port support for Kubernetes svc and ingress
- 6 container host for Openshift
- CentOS 7.6 container host for Kubernetes
- RHEL 7.6 Tranport Node for BMC