Deploy UCT-C Controller Service and Taps

Follow the instructions below to deploy UCT-C Controller Service in your Kubernetes environment using YAML file:

Note:   Contact Technical Support or Contact Sales for the UCT-C images and YAML files.

1. In your Kubernetes orchestrator, edit the UCT-C Controller image name, commands, and other required information into your YAML file. The following is sample data from the YAML file. Edit your YAML file based on the sample given below. Do not copy and paste this content into your YAML file:

   apiVersion: v1
   kind: Service
   metadata:

     labels:

       app: gigamon-uct

       pod: uct-cntlr
       service: uct-cntlr-service
       # change the namespace to match your namespace
     name: uct-cntlr-service
   spec:
     ports:
     - name: uct-rest

       port: 8443
       protocol: TCP    
       targetPort: 8443
     - name: uct-stats

       port: 42042
       protocol: TCP    
       targetPort: 42042
     selector:
       app: uct-cntlr

     type: ClusterIP

   The following table gives a description of all the field values in the YAML file that are updated:

   Field Values	Description
   Port: 443	The UCT-C Controller REST service port number.
   Port: 42042	This port must be port 42042. This allows GigaVUE-FM to communicate with UCT-C to send statistical data.

2. Using the YAML file, Kubernetes creates the UCT-C Controller Service.

Follow the instructions below to deploy UCT-C Controller Service in your Kubernetes environment using YAML file:

Note:   Contact Technical Support or Contact Sales for the UCT-C images and YAML files.

1. In your Kubernetes orchestrator, edit the UCT-C Controller image name, commands, and other required information into your YAML file. The following is sample data from the YAML file. Edit your YAML file based on the sample given below. Do not copy and paste this content into your YAML file:

   name: uct-cntlr
   image: gigamon/uct-cntlr:cntlr-<version>

   command: 

   - # /uct-controller

   - # <GigaVUE-FM IP>

   - # <GigaVUE-FM REST Svc Port>

   - # <UCT-C-Cntlr REST SVC Port>

   env:

   # Service name.Should match name specified in metadata section.
   - name: UCT-C_CNTLR_SERVICE_NAME
    value: "GIGAMON_UCT-C_CNTLR_SERVICE"

   # External LB balancer IP, for controller (FM) to connect to UCT-C-cntlr
   - name: UCT-C_CNTLR_EXT_IP_DNS
    value: "<external IP for GigaVUE-FM to reach UCT-C CNTLR>"

   # K8S cluster end-point (typically, master nodes with default port of 6443)
   - name: K8S_CLUSTER_ENDPOINT
    value: <K8s Cluster API URL>

    -name: UCTC_DEBUG_MODE 

   value: "0x0A000003" 

   # Namespace of Pod

   - name: UCT-C_CNTLR_Tap_NAMESPACE
    valueFrom:
         fieldRef:
             fieldPath: metadata.namespace

   ports:
   - containerPort: 8443

     protocol: TCP
   - containerPort: 42042

     protocol: TCP

   imagePullPolicy: Always

   The following table gives a description of all the field values in the YAML file that are changed or updated:

   Field Values	Description
   /uct-cntlr (image name)	UCT-C Controller image name and version. Make sure to use the latest image version.
   GigaVUE‑FM IP	The IP address of the GigaVUE-FM with which your UCT-C is connected.
   FM REST Svc Port	The FM REST service port number. This must be opened on your Kubernetes to allow outbound traffic. This allows UCT-C Controller to communicate with GigaVUE-FM. Example: 443
   UCT-C-Cntlr REST SVC Port	The UCT-C Controller REST service port number. This must be opened on your GigaVUE‑FM to allow inbound traffic to Kubernetes. This allows GigaVUE-FM to communicate with UCT-C Controller. Example: 8443 (configurable)
   Ports: o containerPort: 443 o containerPort: 42042	Two ports must be opened. The first container port must be the same as UCT-C-Cntlr REST SVC Port. The second container port must be port 42042. This allows UCT-C to send statistical data to UCT-C controller.
   External LB balancer IP	The external load balancer IP/DNS value to allow GigaVUE‑FM to communication with UCT-C Controller within Kubernetes. The GigaVUE‑FM IP entry may change when you upgrade or redeploy.
   K8S cluster end-point	Kubernetes cluster end point for GigaVUE‑FM to access the control plane. UCT supports eight policies per cluster. Example: https://<kubernetesapiserverurl>:6443

2. Using the YAML file, Kubernetes automatically downloads the defined UCT-C Controller Taps and deploys it to the Kubernetes worker node.

Follow the instructions below to deploy UCT-C Controller Service and Taps in your Kubernetes environment using Helm Chart:

Note:   Contact Technical Support or Contact Sales for the UCT-C images and Helm Charts (uct-cntlr-<version>.tgz and uct-tap-<version>.tgz).

1. On your Kubernetes orchestrator, extract the received UCT-C Controller (service and Tap) .tgz package.
   

   $ tar -xvf uct-cntlr-<version>.tgz

2. After extraction, navigate to the uct-cntlr folder and edit the values.yaml file as per your environment. Refer to Deploy UCT-C Controller Service and Deploy UCT-C Controller for detailed information.
3. From the extracted uct-cntlr folder, install the UCT-C Controller Helm using the following command:
   

   $ helm install <Name for the UCT-C Controller> uct-cntlr <Extracted folder path> uct-cntlr/

4. Using the Helm file, Kubernetes creates the UCT-C Controller Service, automatically downloads the defined UCT-C Controller Taps and deploys it to the your worker node.