This is a mirror of the GitLab repository containing the Helm chart that was developed during my internship at Wimma Capstone. Its aim is to deploy PrestaShop on MicroK8s in a reproducible manner. It subsequently became one of the components of my Bachelor's thesis.
Operational but would benefit from some further development
Documentation can be found here: Deploy custom PrestaShop Helm chart (internal repos)
-
Security:
- Add password generation logic. Currently, database password
dbPasswd
and admin dashboard passwordadminPasswd
are declared manually inprestashop/values.yaml
. This approach allows users to update passwords manually if needed, as shown in the attached documentation. However, a better approach would be to generate random passwords using Helm random functions and store them as secrets, which can then be retrieved after deployment with the command that can be provided in theprestashop/templates/NOTES.txt
. This approach is used in Bitnami PrestaShop Helm chart: see - Add pod security context: see
- Add password generation logic. Currently, database password
-
Configurations:
- Helpers (
_helpers.tpl
) require testing and updates - Create a dedicated service account for the MySQL workload. Then, in
templates/mysql-stateful-or-deployment.yaml
line 39, update theserviceAccountName
fromprestashop
tomysql
and test functionality - Service account for the PrestaShop workload should also be reviewed and updated if needed
- Use a custom namespace: see
- Review the autoscaling configuration or remove it if not needed (
prestashop/templates/hpa.yaml
) - Fix the HTTP ingress naming logic, which is currently confusing -
ingress.enabled: false
enables HTTP ingress. - Implement probes: see
- Helpers (