Production test

This contains instructions on how to test the deployed production system on GKE.

Note

Due to the high cost of running GKE and all the services it requires, I am using the average specifications to save costs

Tools and Specs

  • GKE cluster - 1: adidasttestcluster

  • Nodes(compute engine) - 1(due to high cost): gke-adidasttestcluster-default-pool-28f2aa9d-8hh1 with 2CPUs and 3GB

  • Pods - 5(one per service and eventbus)

  • Google cloud build. Triggers a build when code is pushed through skaffold or a build pipeline

  • Google container registry. Manage Docker images, perform vulnerability analysis

  • Google cloud sql - 1: adidas-testdb-instance with 2 CPUs and 4GB

  • Google cloud storage. For storing the built images(can be used to store files if need be)

URLS

  • Use this ip address 34.89.53.39 to create a custom domain or navigate to the Services & Ingress tab on GCP console(access required) and copy the ip of the ingress-nginx-controller external load balancer.

  • Project url is http://www.testadidas.io , however, since no domain has been bought. Run sudo vim /etc/hosts. Then add 34.89.53.39 www.testadidas.io

  • Swagger url http://www.testadidas.io/api/v1/swagger

Note

All urls but three in swagger require a JWT token. Its best to use postman

  • Nats monitoring. Helps monitor which events services are listening to.(this port is only open for testing purposes)

Loading postman

  • Load postman collection by either using this https://www.getpostman.com/collections/b96169c29eb5a9ec6219 or loading the Adidas.postman_collection.json inside the docs folder

  • Signup with any sample credentials

  • Sigin with username and password

  • Copy access token and add it to the postman environment variable JWT or copy paste it manually into the Authorization header as JWT eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9foobar