If you want to expose the services via http://abc.xyz, use loadbalancer type with a DNS record "abc.xyz"
(4) Use JenkinsFile in this repository to create CI/CD Pipeline
To delivery separated in various environment, we will create multiple branches for each environment in this repository and use argoCD to manage those k8s manifest on each branchs
- As for development, we will continuously trigger by merger event from developer to a branch in this repository and deploy it on development envinronment.
- As for staging or UAT we will continuously trigger the build by tagging a version from a set of cherry-pick commit and deploy this tag version onst staging envinronment.
- As for production, we will deploy a specific tag version which been deployed from staging or UAT to deploy to Production envinronment.
CI/CD Architecture
(5) Firstly, we need to deploy a set of monitoring services for this k8s cluster. we can use Prometheus and Grafana.
Prometheus will have us collect all the metrics expose by K8s cluster and the application itself and store it in the database or local file.
Grafana will visualize Prometheus metrics by query them via prometheus API and visualize it in a web UI.
