Deploy UCT Taps

You can deploy the UCT Taps using the YAML files or the Helm Charts. Refer to the following sections for detailed information.

Deploy UCT Taps using YAML files

Follow the instructions below to deploy UCT Taps in your Kubernetes environment using YAML file:

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

  1. In your Kubernetes orchestrator, edit the UCT Tap image name, commands, and other required information in a 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: gigamon-uct
command:
- # /uctapp/uct  
- # (1=> default, 0=> rule)
    - # (1=> L2GRE, 3=> VXLAN)
    env:
    - name: LD_LIBRARY_PATH
     value: /usr/lib64
    - name: UCT_DEBUG_MODE
     value: "0x0A000004"
    - name: UCT_SERVICE_NAME
 value: "UCT_SERVICE"
- name: UCT_CNTLR_SVC_DNS 
  #value: "<UCT-CNTLR-SVC-NAME.UCT-CNTLR-NAMESPACE>.svc.cluster.local" 
  value: "uct-cntlr-service.default.svc.cluster.local"
- name: UCT_CNTLR_REST_SVC_PORT
    # port used to receive configuration from FM
  value: '8443'
    - name: UCT_WORKERNODE_NAME 
    valueFrom: 
    fieldRef: 
    fieldPath: metadata.namespace
    image: gigamon/uct:<version>

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

    Field Value Description
    (1=> default, 0=> rule)(0/1) Enter 1 to use the default destination IP, or enter 0 to use the rules configured by GigaVUE-FM
    (1=> L2GRE, 3=> VXLAN)(1/3) Enter 1 to use the L2GRE tunnel type or enter 3 to use the VXLAN tunnel type.
    gigamon/uct-tap:<version>UCT Controller image name and version. Make sure to use the latest image version.

    UCT_DEBUG_MODE

    The hex value for UCT debugging. This value must be in the 0xdd[aaaa][b][c] format, where:

    • aaaa is a hex value for the number of pcap messages to maintain before rollover

    • b is 0 = do not create pcap or 1 = create pcap

    • c is level. Level with 1 =fatal, 2 =error, 3 =info, 4 =debug

    • dd is the log file size multiplier

      • dd = 0|1 - means default log file size (default 100,000 lines)

      • dd = 08 - means 8 * default log file size (default 8*100,0000 lines)

      • dd = FF = 255 - means (255*100,000 lines)

    UCT_CNTLR_SVC_DNSUCT Controller Service Number. This value must match the metadata used for UCT Controller.
    Example: gigamon-uct-cntlr-service.default.svc.cluster.local
    UCT_CNTLR_REST_SVC_PORTThe UCT Controller REST service port number. This must be opened on your GigaVUE‑FM to allow inbound traffic to Kubernetes.
  2. Using the YAML file, Kubernetes automatically downloads and deploys the defined UCT Taps.

Deploy UCT Taps using Helm Chart

Follow the instructions below to deploy UCT Taps in your Kubernetes environment using Helm Chart:

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

  1. On your Kubernetes orchestrator, extract the received UCT Tap.tgz package.
    $ tar -xvf uct-tap-<version>.tgz
    After extraction, navigate to the uct-tap folder and edit the values.yaml file as per your environment. Refer to Deploy UCT Taps using YAML files for detailed information.
  2. From the extracted uct-tapfolder, install the UCT Helm using the following command:
    $ helm install <Name for the UCT Tap> uct-tap<Extracted folder path> uct-tap/
  3. Using the Helm file, Kubernetes creates the UCT Tap, automatically downloads the defined UCT Taps and deploys it to the Kubernetes worker node.