Containerised hosting on Block Storage

Running containerised hosting on Block storage allows Kubernetes to behave more like a traditional server, with fast local storage shared between containers. Using block storage allows changes to code directly in SSH and using rsync, as well as running all bin/magento commands. This is useful for development and staging environments where quick changes need to be made on the fly.

While a deployment pipeline is still recommended, any deployment methodology is possible.

Disadvantages

When used in production, the use of block storage limits the ability to schedule pods across discrete Kubernetes worker nodes, tying Apache and PHP onto a single node where the block storage is mounted. This limits redundancy to a single node instance, and limits scaling to the size of the applicable worker node. For these reasons we strongly recommend Fully containerised hosting with embedded code for all production environments.