Our great sponsors
-
For the Apache/php container portion and building the app itself, I'd suggest looking at buildpacks (Paketo buildpacks are easy). This can let you standardize on the code->container pipeline. (I'm biased since I'm working on Epinio which uses them to simplify the code->running application pipeline)
-
mysql-operator
Asynchronous MySQL Replication on Kubernetes using Percona Server and Openark's Orchestrator.
+1 for MySQL Operator, however I've never used the "official" one, I deployed several instances with Presslab's https://github.com/bitpoke/mysql-operator I'd say one MySQLCluster for customer (to allow independent version update for the engines).
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Are you working with on-premise compute resources or public-cloud based ones? In the latter case, I'd like to point out the need to choose and deploy an Ingress Controller behind which deploy the PHP-powered sites (to minimize the need for public IPs). If the former, you can easily go with MetaLB https://metallb.universe.tf/ to expose each "site" directly, but an Ingress Controller like Kong, Traefik v2 or others could be however handy to accomodate specific needs (OAuth/JWT to access one or more of these, for example). The PHP-enabled website could be deployed with a "multi-container" Pod/Deployment setup as, for example, described here https://matthewpalmer.net/kubernetes-app-developer/articles/php-fpm-nginx-kubernetes.html
