Overview

1. A fully operational Kubernetes (K8s) cluster. We have tested our solution in AWS Elastic Kubernetes Service (EKS) and Azure Kubernetes Service (AKS). You can also use minikube to test the solution. Google Kubernetes Engine (GKE) was not tested but should work without major issues. All Kubernetes versions tested were >= v1.18

2. MySQL database. Can be deployed inside K8s or use cloud SaaS option. We tested using AWS RDS and Azure Database for MySQL as well as using existing standalone MySQL servers and in-cluster MySQL pods. Tested with v5.6 and v5.7 versions.

3. Redis cache. Can be deployed inside K8s or use cloud SaaS option. We tested with AWS ElastiCache for Redis, Azure Cache for Redis and in-cluster Redis pods.

4. SMTP service. a service user with send permissions or relay server with proper permissions.

5. S3 or MinIO gateway compatible storage.

6. TLS Certificates provisioning (e.g. LetsEncrypt).

7. DNS service. DNS records write access for the deployment domain is required (e.g., Route53, Azure DNS, custom DNS server)

8. Key Management Service. To encrypt/decrypt secrets using helm secrets plugin, See next section for details. Tested with AWS KMS, Azure KeyVault and locally with OpenPGP/GPG