You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scoping the exact requirements and details for the Building of Helm Charts for Postgres and MariaDB
[Implementation] - Buildingof Helm Charts for Postgres and MariaDB
This ticket holds the implementation requirements and details relating to the building of of Helm Charts for Postgres and MariaDB. The LLD details are shown here
1. Summary
It is far better to use a Helm chart which has a lot of the complicated k8s components relating to DBs (Persistent Volume etc.) than to just use the raw Docker container.
This is mainly because DBs require Kuberentes Persistent volumes, Persistent Volume Claims which would take time to configure. Helm charts are also very easy to spin up or spin down.
2. Sources
The Postgres and MariaDB Helm charts can easily be found on Bitnami's repository. We will use that for both local and EKS deployments of PG and MariaDB.
Scoping the exact requirements and details for the Building of Helm Charts for Postgres and MariaDB
[Implementation] - Buildingof Helm Charts for Postgres and MariaDB
This ticket holds the implementation requirements and details relating to the building of of Helm Charts for Postgres and MariaDB. The LLD details are shown here
1. Summary
It is far better to use a Helm chart which has a lot of the complicated k8s components relating to DBs (Persistent Volume etc.) than to just use the raw Docker container.
This is mainly because DBs require Kuberentes Persistent volumes, Persistent Volume Claims which would take time to configure. Helm charts are also very easy to spin up or spin down.
2. Sources
The Postgres and MariaDB Helm charts can easily be found on Bitnami's repository. We will use that for both local and EKS deployments of PG and MariaDB.
3 External Resources
Closing Checklist
The text was updated successfully, but these errors were encountered: