Post Deployment

After you deploy UCT-C Solution in Kubernetes, perform the following for post deployment verification checks:

Verify UCT-C deployment using CLI

Use the following CLI commands to ensure that the UCT-C components are up and running properly within the specified namespace.

1. Check the Controller Deployment:

kubectl get deployment -n <namespace>

This command verifies that the UCT-C controller deployment exists and is running.

2. Check the TAP DaemonSet Status:

kubectl get daemonset -n <namespace>

This command confirms that TAP DaemonSet is running.

3. Verify if the Controller and TAP Pods are Up and Running:

kubectl get pods -n <namespace>

This command displays the current status of the Controller and TAP pods.

4. Confirm the Controller Service is Present and Accessible:

kubectl get svc -n <namespace>

This command confirms that the controller service is correctly deployed and accessible within the cluster.

5. Check the Ingress Resource (if applicable):

kubectl get ingress -n <namespace>

If using the Ingress resource for routing external traffic, use this command to verify the Ingress configuration for the controller.

6. Check the Route Resource (if applicable):

kubectl get route -n <namespace>

If using a Route resource to direct external traffic to the appropriate service in the cluster, use this command to confirm the route configuration.

7. Verify Helm Chart Deployment (if using Helm):

helm list

This command lists the Helm releases deployed in your cluster.

Verify UCT-C deployment using GigaVUE‑FM

You can verify the following interactions between UCT-C and GigaVUE‑FM:

1.   Register UCT-C Controller and TAP
2. Check UCT-C Controller and TAP Status
3. Check UCT-C Controller Connectivity
4. Verify the Cluster Inventory

Register UCT-C Controller and TAP

When a UCT-C Controller and TAP start in the Kubernetes environment, they register directly with GigaVUE‑FM. Check the network requirements for a successful registration. For details, refer to Network Ports Requirements.

UCT-C supports IPv4 and IPv6 protocols. For details, refer to Deploy UCT-C Solution in Kubernetes.

  • When UCT-C Controller and TAP terminate normally, it sends the deregistration message to GigaVUE-FM.

  • If UCT-C Controller and TAP go down abnormally and GigaVUE-FM fails to receive a couple of heartbeats, it will get disconnected.

Check UCT-C Controller and TAP Status

GigaVUE-FM marks the heartbeat status of UCT-C Controller and TAP as Connected when it registers.

  • After successful registration, UCT-C Controller and TAP send heartbeats to GigaVUE-FM every 30 seconds.

  • GigaVUE-FM scans the last received heartbeat of the registered UCT-C Controller and TAP pods and marks the heartbeat status periodically (1 minute).

    Scenarios for heartbeat status:

  • Pending: Missed 2 consecutive heartbeats
  • Disconnected: Missed 3 consecutive heartbeats
  • GigaVUE-FM automatically purges disconnected or terminated UCT-C Controllers and TAPs after a retention period of 7 days.

Note:  GigaVUE-FM generates an alarm for the disconnected UCT-C when three consecutive heartbeats are missed. For details, refer to Alarms.

Check UCT-C Controller Connectivity

After successful registration of UCT-C Controller, GigaVUE-FM periodically checks connectivity to Controller.

Connectivity status:

  • Reachable: If GigaVUE-FM can connect with the UCT-C Controller
  • Unreachable: If GigaVUE-FM cannot connect with the UCT-C Controller

Note:  You should ensure that the UCT-C Controller connectivity is Reachable before configuring it. If the connectivity shown for a UCT-C controller in a cluster is not reachable, the deployment for that cluster does not go through.

Verify the Cluster Inventory

You can navigate to Inventory > CONTAINER > Universal Cloud Tap - Container to verify the UCT-C cluster inventory in GigaVUE‑FM. In the Clusters, Nodes, and Pods sections, you can:

  • Verify that all clusters are listed, operational, and running.

  • Check the cluster's health status, connectivity, and resource usage.