Initialize the AppCenter Cluster | Teradata AppCenter - 1.10 - Initializing the Cluster - Teradata AppCenter

Teradata® AppCenter Customer Installation and Upgrade Guide for vSphere

Product
Teradata AppCenter
Release Number
1.10
Published
June 2020
Language
English (United States)
Last Update
2020-07-02
dita:mapPath
ixs1586886570933.ditamap
dita:ditavalPath
ft:empty
The template .yaml file shown in the following procedure is an example and might not match the file downloaded as part of the actual bundle. The file in the actual bundle is the most up-to-date.
  1. In the override files, add the keys, passwords, and configurations.
  2. Using any standard text editor, open init-override.yaml that was downloaded as part of the AppCenter bundle and make sure the required entries exist:
    consul:
      storageClass: manual
      persistence:
        pv:
          location: /var/lib/docker/teradata/data/consul
      client:
        hostPath: /var/lib/docker/teradata/consul/consul-agent
    
    global:
      nodeSelector:
        nodetype: appcenter
      enableNodeSelector: false
      rook:
        rookEnabled: false
      accessKey: # Refer Table 1.0 - This is a mandatory value
      secretKey: # Refer Table 1.0 - This is a mandatory value
    
    minio:
      persistence:
        pv:
          location: /var/lib/docker/teradata/data/minio
      resources:
        limits:
          cpu: 800m
          memory: 1500Mi
        requests:
          cpu: 500m
          memory: 800Mi
    
    tags:
      minio: true
  3. Add the following key values:
    Table 1.0
    Key Description
    accessKey Needed for Minio's S3 bucket authentication. Alphanumeric string. Minimum size is 3.
    secretKey Needed for Minio's S3 bucket authentication. Alphanumeric string. Minimum size is 8.
    Examples are included in the tar ball.
  4. [Optional] Use this command to generate random char strings for any of the passwords/keys:
    $head /dev/urandom | LC_CTYPE=C tr -dc A-Za-z0-9 | head -c <NUMBER-OF-CHARACTERS> ; echo ''
  5. Initialize the cluster:
    $ appctl init --chart init-1.10.0+build.78.83d5fe3.tgz --images init-image-bundle-1.10.0+build.17.97cd1ca.tar.gz -f init-override.yaml --reset-values
  6. Make sure all the pods are in "Running"/"Completed" state:
    $ kubectl get pods --all-namespaces

    Type use appctl init -h for more details on parameters that can be used as part of the init command.

  7. Upload the Docker images that will be used to bring up all AppCenter services:
    $ appctl upload --images platform-image-bundle-1.10.0+build.17.97cd1ca.tar.gz
    $ appctl upload --images appcenter-image-bundle-1.10.0+build.17.97cd1ca.tar.gz
    The images are pushed to the Docker registry that was part of initializing the cluster.
  8. [Optional] For more details on parameters that can be used as part of the upload command, run:
    appctl upload -h