Feature request: Kubernetes-specific container

[9joshua]

Some suggestions from a customer which might work well if we had a Kubernetes-specific version of the Matomo docker container:

The container as produced is almost friendly for running with no PVC at all, enabling cheaper and more effective scaling. If the config data was moved to the database and it could operate without it entirely by just environment variables to reach it, it'd be able to operate better in a kubernetes context.

In a common kubernetes environment, the ingress routing can likely be handled by an ingress, removing the need to have apache in the container.

[BenGig]

All files should be extracted during image build, not during the initial startup. Self modifying images are uncommon and against the idea of immutability. Pods (containers) come and go on Kubernetes, the frequent unpacking causes delays and unnecessary load on the system. And it wastes storage: images are shared between container, but not the additional layer caused by the local extraction.