Testing the HTTPS Client Call

To test the HTTPS Client call, start testing traffic using CURL:
  1. From within the Cluster Manager CLI container:
    [root@cm-deploy-0-76ffbdbb6b-jjb44 builder]# clustermanager ls components
    Using cluster [Tibco Mashery Local Reference Cluster]
    Using Zone [local]
    Component ID                          Component Type       Component Name       Component Status     Component Host       Component Agent Port   Component Service Port(s)
    ------------------------------------- -------------------- -------------------- -------------------- -------------------- ---------------------- ---------------------------
    0adf6ab7-19a3-4598-9c4e-f9e20729448f  sql                  sql                  ACTIVE               10.244.1.5           9080                   3306
    bd465cb3-2c19-4b89-afc8-f4719cd43d7b  nosql                nosql                ACTIVE               10.244.1.2           9080                   9042
    37e880ce-6d05-4a6f-bdae-cee24a70b6a0  cache                cache                ACTIVE               10.244.1.6           9080                   11212,11211,11213,11214,11215,11216
    f8f6da07-6669-413c-b356-cdb26be4f4df  trafficmanager       tm                   ACTIVE               10.244.1.7           9080                   8080
    74062084-0d77-4a43-9551-07db90e8fdd9  logservice           log                  ACTIVE               10.244.1.4           9080                   24224
     
    [root@cm-deploy-0-76ffbdbb6b-jjb44 builder]# curl -H 'Host:api.example.com'  'http://x.x.x.x/hw_path_01?api_key=sra663fmnshjazx5sv2mgtmw'
    {"time":"2018-11-28 20:17:02.841+0000","message":"Hello world"}
  2. From load balanced TM service:
    Note: Note the Kubernetes service for the Traffic Manager ("tm-svc" in this case).
    admin-MBP15:properties <admin>$ kubectl get svc
    NAME          TYPE           CLUSTER-IP      EXTERNAL-IP        PORT(S)                                     AGE
    cass-svc-0    ClusterIP      None            <none>             9042/TCP                                    16h
    kubernetes    ClusterIP      100.64.0.1      <none>             443/TCP                                     17h
    log-svc-0     ClusterIP      None            <none>             24224/TCP                                   16h
    mysql-svc-0   ClusterIP      None            <none>             3306/TCP                                    16h
    tm-svc        LoadBalancer   100.71.130.12   a45e45c83f2cb...   80:32299/TCP,443:32117/TCP,8083:31296/TCP   16h
     
     
    admin-MBP15:properties <admin>$ kubectl describe service tm-svc|grep Ingress|awk -F' ' '{print $3}'
    a45e45c83f2cb11e8bc330609f0835b9-95933830.us-east-1.elb.amazonaws.com
     
    admin-MBP15:properties <admin>$ curl -H 'Host:api.example.com'  'http://a45e45c83f2cb11e8bc330609f0835b9-95933830.us-east-1.elb.amazonaws.com/hw_path_01?api_key=sra663fmnshjazx5sv2mgtmw' -k
    {"time":"2018-11-28 21:15:04.540+0000","message":"Hello world"}