Architecture of Universal Cloud Tap - Container

The following diagram illustrates the architecture of Universal Container Tap environment.

1. The UCT-C Tap is registered with GigaVUE-FM through the UCT-C Controller
2. GigaVUE-FM deploys the traffic policy on the UCT-Cs.
   Communication of configuration, data, and statistics to and from UCT-C is performed through the UCT-C Controller Service. GigaVUE-FM communicates with the UCT-C Taps through the UCT-C Controller. GigaVUE‑FM deploys the traffic policy on UCT-C and receives the statistics from UCT-C tap through UCT-C controller.
3. The customer workload collects the network traffic and sends the network packets to the Kernel space.
4. The Kernel space filters the packets based on the rules and filters.
5. The filtered network packets are tunneled directly to the Tools or through the GigaVUE V Series nodes running on any supported GigaVUE Cloud Suite on cloud environment.
6. The UCT-C Controller collects the data from UCT-C Taps and sends the collected statistics and heartbeats to GigaVUE-FM.