Deploying a Cluster in AWS using Kubernetes

  1. Change to folder "manifest-single-zone" or folder"manifest-multi-zones", run the following command to create Kubernetes cluster: 
    ./create-k8s-cluster.sh
    Note: The creation of Kubernetes cluster in AWS takes a couple of minutes; in the beginning, information such as the following, shows AWS EC2 instances are being initialized: 
    unexpected error during validation: error
listing nodes: Get https://api-82639c304b69c40a9b598-61u3ae-1931300466.us-east-1.elb.amazonaws.com/api/v1/nodes:
EOFUsing cluster from kubectl context:
82639c304b69c40a9b598c6ae694f731.k8s.local
    Example output of a successful Kubernetes cluster creation on AWS: 
    Using cluster from kubectl context: 5ed6d343eea46b68a91c435070f6d00d.k8s.local
 
Validating cluster 5ed6d343eea46b68a91c435070f6d00d.k8s.local
 
INSTANCE GROUPS
NAME            ROLE    MACHINETYPE MIN MAX SUBNETS
master-us-east-1d-1 Master  m3.medium   1   1   us-east-1d
master-us-east-1e-1 Master  m3.medium   1   1   us-east-1e
master-us-east-1e-2 Master  m3.medium   1   1   us-east-1e
nodes           Node    m3.large    6   6   us-east-1d,us-east-1e
 
NODE STATUS
NAME                ROLE    READY
ip-172-20-34-70.ec2.internal    node    True
ip-172-20-40-103.ec2.internal   node    True
ip-172-20-54-108.ec2.internal   master  True
ip-172-20-61-236.ec2.internal   node    True
ip-172-20-68-207.ec2.internal   node    True
ip-172-20-69-168.ec2.internal   node    True
ip-172-20-77-195.ec2.internal   master  True
ip-172-20-85-209.ec2.internal   master  True
ip-172-20-95-174.ec2.internal   node    True
 
Your cluster 5ed6d343eea46b68a91c435070f6d00d.k8s.local is ready
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Login Succeeded
  2. Load and upload Docker images.
    Run the following command to load Docker images locally: 
    ./load-images.sh
path_to_docker_image_files
    Note: When deploying TIBCO Mashery Local cluster in the installer, Docker images are already loaded after a successful build. The above step can be skipped.
    Run the following command to upload Docker images to the AWS repository: 
    ./upload-images.sh
    Run the following command to set registry secret in AWS: 
    ./set-registry-secret.sh
  3. Create the TIBCO Mashery Local cluster.
    Run the following command to create the TIBCO Mashery Local cluster: 
    ./create-tml-cluster.sh