Post Deployment

Refer to the sections listed below for post deployment verification checks after deploying UCT-C Solution in Kubernetes.

Verify UCT-C deployment using CLI

You can verify the UCT-C deployment using the following CLI commands to ensure that the UCT-C components are up and running as expected within the specified namespace.

1. Check for the Controller Deployment:

kubectl get deployment -n <namespace>

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

2. Verify the TAP DaemonSet Status:

kubectl get daemonset -n <namespace>

This command checks the status of the TAP DaemonSet, ensuring that it is properly deployed.

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

kubectl get pods -n <namespace>

This command checks that the controller and TAP pods are running and available.

4. Confirm the Controller Service is Present and Accessible:

kubectl get svc -n <namespace>

Run this command to confirm 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 you are 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 come up in the Kubernetes environment, it registers itself with GigaVUE‑FM.

Check the network requirements for the registration to be successful. Refer to Network Ports Requirements.

UCT-C supports IPv4 and IPv6 protocols. Refer to Deploy UCT-C Solution in Kubernetes.

When UCT-C Controller and TAP is terminated normally, it sends the deregistration message to GigaVUE-FM. If UCT-C Controller and TAP goes 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 gets registered. After successful registration, UCT-C Controller and TAP sends 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). The following are the various scenarios where the heartbeat status changes:

  • If 2 consecutive heartbeats are missed, GigaVUE-FM marks the status as Pending.
  • If 3 consecutive heartbeats are missed, GigaVUE-FM marks the status as Disconnected.
  • 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. Refer to Alarms.

Check UCT-C Controller Connectivity

After successful registration of UCT-C Controller, GigaVUE-FM periodically checks connectivity to Controller. The following are the various scenarios where the UCT-C Controller connectivity changes:

  • If GigaVUE-FM can connect with the UCT-C Controller, the connectivity status will be marked as Reachable.
  • If GigaVUE-FM cannot connect with the UCT-C Controller, the connectivity status will be marked as Unreachable.

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

Verify the Cluster Inventory

You can verify the UCT-C cluster inventory in GigaVUE-FM by navigating to Inventory > CONTAINER > Universal Cloud Tap - Container. In the Clusters, Nodes, and Pods sections you can verify that all clusters are listed, operational, and running. You can also check the cluster's health status, connectivity and resource usage.