Skip to content

Latest commit

 

History

History
73 lines (51 loc) · 2.83 KB

run-options.md

File metadata and controls

73 lines (51 loc) · 2.83 KB
Raw

Run Options

Note: For all environments, you can use files under the .postman folder to test the application. Test users to login are listed below.

E-Mail Password Role
vader_666@mail.com i_hate_sand CUSTOMER, MANAGER
malvo_lrn@mail.com sioux_falls CUSTOMER
peaky_blinder@mail.com garrison_1918 CUSTOMER

Development

This mode will start Postgres, Redis, RabbitMQ, APISIX and Keycloak as containers in Docker. You can start the microservices with your IDE.

docker-compose -f .docker/docker-compose.yaml up -d

Test

This mode will start the whole application in a K8S cluster. You can test it on your own computer if you enable Kubernetes on Docker Desktop or OrbStack.

Make sure ArgoCD is installed on your cluster.

kubectl create -f ./.kubernetes/Root.yaml

Production

This mode will start the entire application on AWS. A Kubernetes cluster will be created from scratch (including network and nodes) and databases will be created from their previous snapshot.

The provisioning of this environment has a pipeline on AWS that consists of 3 stages. All configurations are inside .ci/production folder.

Note: I am using my own domain name (solidvessel.com) so you must set up your own domain in the configuration files.

1) Kubernetes Cluster

In the first build stage, create-cluster.yaml and cluster.yaml files are used to create the K8S cluster. You can change them according to your own needs. Make sure you have necessary IAM permissions.

2) Databases

The second build stage is responsible from creating databases by using Cloudformation. In the databases.yaml file there are also configurations to handle DNS and firewall rules to establish a connection between worker nodes and databases.

The databases are created from snapshots, meaning the data is not lost when they are down. If this is your first setup, you must change the databases inside databases.yaml, so they are going to be created from scratch.

3) Applications

In the final stage ArgoCD is installed and the rest of the applications (microservices, Redis, RabbitMQ...) are created. In addition to the applications in the test environment, tools like External DNS and AWS Load Balancer Controller also created in this environment. Bitnami Postgres applications will not be created since RDS Postgres databases are used.

Aftermath

After all stages are finished, the production environment will be ready to use and microservices will be publicly accessible. Tools like Keycloak and ArgoCD are not publicly accessible, and you should use kubectl port-forward for them.