Deis Workflow, now in Beta!
Your PaaS. Your Rules.
Unleash your apps with the leading Kubernetes PaaS.
$ ^300 helm install deis/workflow
$ ^400 deis create
$ ^400 git push deis master ^800
$ ^400 deis scale web=10
$ ^400 deis config:set POWERED_BY=Kubernetes
Compressing, writing objects...Creating application... 100% done.
-----> sanest-lakeside deployed to Deis.
-----> Building Docker image
So What is Deis Workflow?
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.
Why Use Workflow?
Fast & Easy
Supercharge your team with a platform that deploys applications as fast as you can create them.
Benefit from the latest distributed systems technology thanks to a platform that is constantly evolving.
Fully Open Source
Maintain your independence with an open source platform that runs on public cloud, private cloud or bare metal.
What Are Users Saying?
Recent Blog Posts
27 May 2016
Kubernetes is a very popular open source container management system.
The goal of the Kubernetes project is to make management of containers across multiple nodes as simple as managing containers on a single system. To accomplish this, it offers quite a few unique features such as traffic load balancing, self-healing (automatic restarts), scheduling, scaling, and rolling updates.
In this post, we'll learn about Kubernetes by deploying a simple web application across a multi-node Kubernetes cluster. Before we can start deploying containers however, we first need to set up a cluster.
26 May 2016
This release marks the first in the Helm 2 line. It is an unstable Alpha-quality release that supports the core functionality for the Helm 2 platform.
Helm 2 has two major components:
- The Helm client, whose responsibility is to provide tooling for working with charts and uploading them to the server.
- The Tiller server, whose responsibility is to manage releases into the Kubernetes cluster.
Additionally, Helm can fetch charts from remote repositories. A Helm 2 chart repository is simply an HTTP server capable of serving YAML and TGZ files.
As a developer preview, the Alpha 1 release does not have a binary build of its components. The quickest route to get started is to fetch the source, and then run
make bootstrap build. To start using Helm, use
Stay in touch
To keep up with news on Helm, join the #Helm channel on the Kubernetes Slack channel, or join our weekly developer call every Thursday at 9:30-10:00 Pacific.
You are welcome to join! https://engineyard.zoom.us/j/366425549
During the May Deis Community meeting I took a few moments to talk about the general direction and core values for the Helm project. Click play for my presentation:
20 May 2016
This guide is targeted to the Deis v1.13 LTS branch. With over 6 million downloads, Deis V1 PaaS has never been more popular. These instructions will not work with Deis Workflow, the Kubernetes-native PaaS, which is still currently in beta.
I am going to demo a cheap, quick, and dirty way to bring up a cluster for Deis V1 PaaS on DigitalOcean. This is the cheapest fault-tolerant configuration that I could manage. That is, a cluster on which some nodes can go down—but the cluster and its platform services remain available!
Before we go on, let's distinguish fault-tolerant from highly available.
Fault-Tolerant or Highly Available?
A fault-tolerant Deis cluster continues operating, even in the event of some partial or complete failure of some of its component nodes. This guide will show you how even a cheap Deis cluster can be fault tolerant—and to what extent.
A highly available (HA) Deis cluster is one that is continuously operational, or never failing. HA is the harder of the two to achieve, and this tutorial won't show you how to do that.
High availability is something that isn't provided out-of-the-box in most cases. If HA is one of your goals, your sysadmin or dev team will be better qualified to say what obstacles you will face in maintaining a standard of high availability for your apps.
19 May 2016
As we've covered before, shared file systems are a tricky problem in the cloud. One solution to that problem is a distributed file system. Something each one of your app nodes can read from and write to. When it comes to distributed file systems, GlusterFS is one of the leading products.
With a few simple scripts on your Mac OS X or Linux machine, you can deploy a multi-zone High Availability (HA) GlusterFS cluster to Google Compute Engine (GCE) that provides scalable, persistent shared storage for your GCE or Google Container Engine (GKE) Kubernetes clusters.
In this post, I will demo these scripts and show you how to do this. By default, our GlusterFS cluster will use three GlusterFS servers, one server per Google Cloud zone in the same chosen region.
11 May 2016
Another few weeks, another Deis Workflow beta!
And what good is a changelog if it doesn't come with a soundtrack? Maybe a little "Crazy on You" by Heart...