Deploy GCB Controller Service and Pods

Follow the instructions below to deploy GCB Controller Service in your Kubernetes environment using the YAML file.

Note:  For the GCB images and YAML files, Contact Sales

1. In your Kubernetes orchestrator, edit the GCB Controller image name, commands, and other required information into your YAML file.
   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:
     name: gigamon-gcb-cntlr-service
     labels:
       app: gcb-cntlr
       service: gigamon-gcb-cntlr-service
       # change the namespace to match your namespace
     namespace: default
   spec:
     ports:
     - port: 8443
       protocol: TCP
       name: gcb-rest
       targetPort: 8443
     - port: 42042
       protocol: TCP
       name: gcb-stats
       targetPort: 42042
     selector:
       app: gcb-cntlr

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

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

2. Using the YAML file, Kubernetes creates the GCB Controller Service.

Follow these instructions to deploy GCB Controller Service in your Kubernetes environment using YAML file:

Note:  Contact Technical Support or Contact Sales for the GCB images and YAML files.

1. In your Kubernetes orchestrator, edit the GCB Controller image name, commands, and other required information into your YAML file.
   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: gcb-cntlr
   image: gigamon/gcb-cntlr:cntlr-<version>

   command: 

   - # /gcb-cntlr

   - # <FM IP>

   - # <FM REST Svc Port>

   - # <GCB-Cntlr REST SVC Port>

   - # <mTLS Mode: 1(ON)|0(OFF))

   - # <Cert Path>

   - # <Cert file>
   - # <Pvt Key>
   - # <CA-Root>

   imagePullPolicy: Always

   ports:
   - containerPort: 8443
   - containerPort: 42042

   env:

   # Service name.Should match name specified in metadata section.
   - name: GCB_CNTLR_SERVICE_NAME
    value: "GIGAMON_GCB_CNTLR_SERVICE"

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

   # K8S cluster end-point
   - name: K8S_CLUSTER_ENDPOINT
    value: "https://<kubernetesapiserverurl>:6443"
   # Namespace of pod

   - name: GCB_CNTLR_POD_NAMESPACE
    valueFrom:
         fieldRef:
             fieldPath: metadata.namespace

   Field values in the YAML file that are changed or updated:

   Field Values	Description
   /gcb-cntlr (image name)	GCB Controller image name and version. Make sure to use the latest image version.
   GigaVUE‑FM IP	The IP address of GigaVUE‑FM with which your GCB is connected.
   FM REST Svc Port	The GigaVUE‑FM REST service port number. Opened the port on your Kubernetes to allow outbound traffic. This allows GCB Controller to communicate with GigaVUE‑FM. Example: 443
   GCB-Cntlr REST SVC Port	The GCB Controller REST service port number. Ope this port on your GigaVUE‑FM to allow inbound traffic to Kubernetes. This allows GigaVUE‑FM to communicate with GCB Controller. Example: 8443
   mTLS Mode: 1(ON) | 0(OFF)	To specify if mTLS mode between GigaVUE‑FM and GCB controller should be On or Off. Values are: 1 - ON 0 - OFF
   Cert Path	Path of the certificate file. Example: /etc/gcbcerts
   Cert file	Name of the certificate file. Example: gcb-cert.pem
   Pvt Key	Name of the private key. Example: gcb-pvt-key.pem
   CA-Root	Name of the CA root certificate. Example: gcb-ca-root-cert.pem
   Ports: ● containerPort: 8443 ● containerPort: 42042	You must open both the ports. Ensure that the first container port is the same as GCB-Cntlr REST SVC Port. Ensure that the second container port is port 42042. This allows GigaVUE‑FM to communicate with GCB to send statistics data.
   External LB balancer IP	The external load balancer IP/DNS value to allow GigaVUE‑FM to communication with GCB 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. Example: https://<kubernetesapiserverurl>:6443

   Note:  Volume Mount is optional for the cases when there is no mTLS authentication. You should enter your volume mount path and a name for the volume mount. For detailed information, refer to the respective YAML files.

2. Using the YAML file, Kubernetes automatically downloads the defined GCB Controller Pods and deploys it to the Kubernetes worker node.

Follow these instructions to deploy GCB Controller Service and Pods in your Kubernetes environment using Helm Chart:

Note:  Contact Technical Support or Contact Sales for the GCB images and Helm Charts (gcb-cntlr-<version>.tgz and gcb-http-<version>.tgz).

1. On your Kubernetes orchestrator, extract the received GCB Controller (service and Pod) .tgz package.
   

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

2. Navigate to the gcb-cntlr folder and edit the values.yaml file as per your environment. For details, refer to Deploy GCB Controller Service and Deploy GCB Controller Pods.
3. From the extracted gcb-cntlr folder, install the GCB Controller Helm Chart using the following command:
   

   $ helm install <Name for the GCB Controller> <Extracted folder path>

   Example: $ helm install gcb-cntlr gcb-cntlr/

   Using the Helm file, Kubernetes creates the GCB Controller Service, automatically downloads the defined GCB Controller Pods and deploys it to the Kubernetes worker node.