Creating a Local Edition Cluster

Prerequisites

Ensure the OpenShift cluster set up is ready for deployment. Edit the reference deployment file docker-deploy/onprem/openshift/manifest-single-zone.json
Below are the cluster level properties:
  • "tml_cluster_name": "Local Edition Gateway Reference Cluster",
  • "tml_cluster_mode": "untethered",
  • "tml_zones": ["local"]
Specify valid value for "tml_cluster_mode". Following are the only two valid values.
  1. tethered : In this mode, TIBCO Cloud™ API Management - Local Edition gets the configuration data from API Management - Local Edition cloud (You need to have MOM Key and Secret in this mode).
  2. untethered : In this mode, you configure data through ML config manager UI.

Procedure

  1. Navigate to the /docker-deploy/onprem/openshift /manifest-single-zone/ folder.
  2. Login the OpenShift server. 
     oc login <openshiftConsoleUrl> || export KUBECONFIG=<path to kubeconfig>
  3. Create new project. 
    oc new-project <project name>
    For example, oc new-project ml5-openshift.
  4. Update k8s_deploy_namespace: <project name> in the docker-deploy/onprem/openshift/manifest-single-zone.json file.
  5. Ensure a service account is available in the namespace and mapped to the appropriate scc.
  6. Get container registry username and the password.
  7. Create a registry secret to being used by docker to pull images during deployment. 
    oc create secret docker-registry \
    --docker-server=894547326815.dkr.ecr.us-east-1.amazonaws.com \
    --docker-username=<username> \
    --docker-password=<password> \
    tmgc-registry-key
  8. Create the cluster. 
    ./create-tml-cluster.sh
  9. Verify the deployment in Onpremises Openshift cluster: 
    oc get pods
    Example output 
    NAME                  READY     STATUS    RESTARTS    AGE
 
cache-set-0-0                  1/1       Running   0          21h
 
cass-set-0-0                   1/1       Running   0          21h
 
cm-deploy-0-fdc68b486-z6m4k    1/1       Running   0          21h
 
log-set-0-0                    1/1       Running   0          21h
 
mysql-set-0-0                  1/1       Running   0          21h
 
tm-deploy-0-596d986875-lk5sf   1/1       Running   0          21h

What to do next

Validate the cluster