This applicatio contains a set of microservices and can be run in 3 ways as explained below:

Go to the directory with yaml file and > docker-compose up

> docker-compose up -d

1. docker run -d -p 8161:8161 -p 61616:61616 --name myqueue --network locationtracker guptavinodkumar/lt-activemq:0.0.1-RELEASE

2. docker run -d --network locationtracker --env spring.activemq.broker-url=tcp://myqueue:61616 --env fleetman.position.queue=positionQueue guptavinodkumar/lt-position-simulator:0.0.1-RELEASE

3. docker run -d -p 27017:27017 --name mongodb --network locationtracker mongo:3.6.5-jessie

4. docker run -d -p 8090:8090 --name positiontracker --network locationtracker --env spring.activemq.broker-url=tcp://myqueue:61616 --env fleetman.position.queue=positionQueue --env spring.data.mongodb.host=mongodb guptavinodkumar/lt-position-tracker:0.0.1-RELEASE

5. docker run -d -p 8080:8080 --name apigateway --network locationtracker --env position-tracker-url=http://positiontracker:8090 guptavinodkumar/lt-api-gateway:0.0.1-RELEASE

6. docker run --network locationtracker -p 80:80 --env SPRING_PROFILES_ACTIVE=local-microservice guptavinodkumar/lt-webapp:0.0.1-RELEASE

1. Create cluster in AWS using : https://docs.google.com/document/d/1fb3k7rgK9HFWktL-R43pwTbXQUGxsZi7pmHA0By-quQ/edit#
2. The folder yaml-files contains all the yaml documents requiered to build pods/servcies.
3. Ignore test.yaml (that was only for testing a piece of microservices)

COMPONENTS:

MASTER NODE:

• API Server: Exposes APIS for all the operations in K8s. For interaction either use kubectl or K8s UI
• Scheduler: Physically schedules pods across multiple nodes - basis the configurations provided (like CPU,Memory,Instance Type etc)
• etcd : Distributed ligthweight Key-Value Db. Containing current state of Clusterat any point of time. It is Single Source of Truth
• Controller Manager : Responsible for health of entire cluster. Actually 4 backing cotrollers -
  • Node Controller
  • Replication Controller
  • Endpoint Controller
  • Service Account and Token Controller

WORKER NODE:

• Kubelet: Primary Node Agent that runs on each Worker Node. It looks at the Pod Spec(YAML) and ensures that cotainers described are healthy and running.
• Kube Proxy: Responsible for mainting all network configurations -across all pods/nodes. Also exposes services to outside world.
• Pods & Containers