Deploy UCT-C on Redhat Openshift Platform using Openshift UI

You can deploy the UCT-C Controller and TAPs in the Redhat Openshift Platform using Helm Charts. For details, refer to the following topics.

Prerequisites

■   To deploy, you should have Developer access in Redhat Openshift Platform.
■   To validate the deployment, you should have Administrator access.
■   In Redhat Openshift Platform, you should create service account and add it to privileged access (use the below command). Use that service account in values.yaml that allows uctc-tap to come up as a privileged pod.

oc adm policy add-scc-to-user -z <service_account> <privileged_scc> -n uctc

Deployment of UCT-C Controller and TAPs

To deploy UCT-C Controller and TAPs, follow these steps:

  1. Log in to the Redhat Openshift online platform using your Redhat login credentials.

  2. Switch to Developer access in the drop-down on the top of the page.

  3. Navigate to the Helm section.

  4. Select Create > Helm Release.

    The Helm Charts screen appears.

  5. Browse and select Gigamon from the All items search menu.

  6. On the Gigamon-UCT-C landing page, select Create.

    Create Helm Release page appears.

    Note:  The README content on the Gigamon-UCT-C landing page provides information on how to deploy UCT-C Controller and Tap on a Kubernetes cluster using Helm Chart.

  7. To create Helm Release, enter or select the required information as described in the following table.

Section

Field

Description
 

Release Name

Specify the Helm Release name.

Chart Version

Select the appropriate release version from the drop-down menu. By default, the latest uploaded version of the release is displayed.

Configure via

Select between Form view and YAML view.

 

Gigamon UCT-C Configuration

 

imagePullSecrets

Specify the created secret name.

 

 

 

 

 

 

 

 

uctcTap

resources - crisocketvolume

Specify the socket location details.

Note:  The socket location for commonly used CRIs are as follow:
docker - /var/run/docker.sock
containerd - /var/run/containerd/containerd.sock
cri-o - /var/run/crio/crio.sock

ingress

Specify the following details in the ingress section:

● enabled - Click the check box to enable
● className - Specify the class name
● annotations - Specify the annotations details (kubernetes.io/ingress.class and nginx.ingress.kubernetes.io/backend-protocol).

serviceAccount

Enable the Create option and specify the serviceAccount name.

 

 

 

 

 

 

 

uctcController

 

resources

Specify the port value.

certs

Specify the following details in the uctcController section:

● ext_load_balancer - The external load balancer IP/DNS value to allow GigaVUE‑FM to communicate with UCT-C Controller within Kubernetes.
● k8s_cluster_url - Kubernetes cluster end point for GigaVUE‑FM to access the control plane.
Example: https://<kubernetesapiserverurl>:6443

service Name

Specify the service label name.

Example: uctc-cntrl-service

image

Specify the following details in the image section:

● repository
● pullPolicy

fm_ip

Update the fm_ip detail.

 

namespace

Update the namespace detail.

  1. Select Create to deploy the UCT-C solution.

  2. To validate the deployment, switch to Administrator view and navigate to:

    ■   DaemonSets option to validate the UCT-C-Tap deployment.
    ■   Deployment option to validate the UCT-C-Controller deployment.