Note about Creating Kubernetes and Mashery Local Clusters

If you plan to upgrade to a newer version of Mashery Local within a short timeframe, perform the following steps for creating your Kubernetes and Mashery Local clusters to ensure a smoother go-live.

  1. Create the Kubernetes cluster: 
    create-k8s-cluster.sh
  2. Create the Mashery Local cluster: 
    create-tml-cluster.sh
  3. Check that the cluster is created successfully.
  4. Check that the sync is successful.
  5. Run traffic calls against the randomly generated TM-service load balancer IP, for example: 
    [root@1paspmascen7a1 manifest-single-region]# kubectl describe service tm-svc | grep -i loadba

    Type: LoadBalancer Load

    Balancer Ingress: 52.229.18.225
  6. Create service, endpoints, pacakge, plan, applications and keys.
  7. Verify that end to end use cases work as expected to confirm that the clusters are okay.
  8. Generate static IPs for Configuration Manager and Traffic Manager service by running: 
    create-static-ips.sh
    This updates the tm-svc.yaml with a static IP address for the load balancer IP: 
    Load Balancer IP: 1.2.3.4
  9. Map the static IP address to the domain name (api.customer.com).
  10. Run the following command to re-provision TM pods with above changes in the .yaml file: 
    kubectl apply -f tm-svc.yaml
    Now api.customer.com traffic should be routed to the newer Mashery Local cluster with zero traffic calls failing. For example, if upgrading from Mashery Local 5.2 to 5.3, traffic should be served by the 5.3 cluster instead of the 5.2 cluster, and during the brief time of switch, no traffic should fail.