Demystifying ncp workflow
NCP is the container plugin for NSXT, there could be number of articles about NCP architecture already existing, I intend to cover only the areas that lack coverage, example hyperbus internals in upcoming posts. In this post we will see what happens on NSXT side when you create resources on the kubernetes side. To ramp-up let me give a quick intro about NCP components. NCP pod: This is the core piece of NCP solution. It watches k8s events and talks to NSXT MP to facilitate the resource creation. It can run as a pod or as a process(in PKS environments) Nsx-Node-agent: Node-agent is an infra pod(this can also run as a process), runs as a daemonset .so each nodevm will get a replica of node-agent pod. As of NCP 2.5 It has 3 containers/components . i) nsx-node-agent ii)nsx-kube-proxy iii) nsx-ovs nsx-node-agent container takes care of plumbing the network interfaces onto workload pods. nsx-kube-proxy watches service creation events from k8s api and progr...
