Deploy GCB Controller PODs

Follow the instructions below to deploy GCB Controller Service in your Kubernetes environment:

Note:  Contact 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. The following is sample data that can be entered in your 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:gcb-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

    The following table gives a description of all the 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 the GigaVUE-FM with which your GCB 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 GCB Controller to communicate with GigaVUE-FM.
    Example: 443

    GCB-Cntlr REST SVC Port

    The GCB 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 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 fileName of the certificate file.
    Example: gcb-cert.pem
    Pvt Key

    Name of the private key.
    Example: gcb-pvt-key.pem

    CA-RootName of the CA root certificate.
    Example: gcb-ca-root-cert.pem

    Ports:

    o containerPort: 8443
    o containerPort: 42042

    Two ports must be opened. The first container port must be the same as GCB-Cntlr REST SVC Port. The second container port must be 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

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