Running Deis Workflow with Minio
Deis Workflow is an open source PaaS that makes it easy to deploy and manage applications on your own servers. Workflow builds upon Kubernetes and Docker to provide a lightweight PaaS with a Heroku-inspired workflow. Workflow is implemented as a variety of self-contained components (see https://github.com/deis for a list) which communicate using both the Kubernetes system and an object storage server. It's configurable to use cloud object storage systems like Amazon S3, Google Cloud Storage and Microsoft Azure Storage and, of course, Minio. We don't yet recommend you use Minio in production Deis Workflow installations, we do recommend it as a great way to quickly install a Deis Workflow cluster for a quick demo, development, testing, etc. In fact, we ship Deis Workflow with Minio installed by default.
To use it, follow the instructions at https://docs-v2.readthedocs.io/en/latest/installing-workflow/. Once you've completed the installation, follow any of the three methods for deployment listed below:
All of the three deployment methods, as well as Workflow internals use Minio extensively behind the scenes:
- Buildpack deployments use Minio to store code and slugs
- Dockerfile deployments use Minio to store Dockerfiles and associated artifacts
- Docker Image deployments use Minio as the backing store for the internal Docker registry that Workflow runs
- The internal Workflow database stores user login information, SSH keys, and more. It backs all data up to Minio