CI-CD
Here the DevOps practices and methodologies that we have in Greenstand
Continuous Integration
The goal is to build and deploy the application per environment (development, test and production). Every application or micro-service should has at least one continuous integration job.
At the end of a successful build process, the deployable artifact is archived and stored in GitHub asset management with a version matching the for use during deployment, using semantic versioning.
Continuous Deployment
The deployment process is dependent on CI. The deployment is into the Digital Ocean clusters via kustomize
Supporting CI-CD there are workflows templates created:
As a solution to encrypt our secrets:
Kubeseal for secrets: sealed-secrets
For how services are reached (i.e. ingress)
A reverse proxy exists for our services controlled by Ambassador
DNS is set with terraform in our Digital Ocean account
For how our services are monitored, monitoring is split among three pieces
Prometheus + Grafana for metrics
Jaeger for traces
Elasticsearch + Kibana for logs
Last updated