6 Jun 2016
The Deis Workflow team is as happy as a baby goat jumping off stuff during spring time. We just cut Release Candidate 2 of Deis Workflow!
While we are busy leaping off things in fits of glee, give Deis Workflow RC2 a shot.
We've been generally cleaning house and closing bugs. There are a few changes that we want to highlight for this release candidate.
Private Image Support
We shipped private image support in Workflow Beta 3. For RC2, instead of always pulling the remote images to the managed on-cluster registry, we now use ImagePullSecrets baked into Kubernetes. This means your private images will be pulled directly to the nodes. Usually good advice to go direct to the source concerning private matters, no?
New name for Release ENV vars
If your application is utilizing the
DEIS_RELEASE environment variable you will need to update your application. In a bout of house cleaning, we've switched that over to
WORKFLOW_RELEASE, it is Deis Workflow afterall. We've updated all our example apps as well, because bug free demos are always nice to see.
Ubuntu Slim, so thin!
Through the beta phase we repeatedly observed a number of DNS failures both on our end-to-end testing infrastructure and our development installs. Through a long and twisty maze of bugs, this boiled down to a bug in ulibc's DNS resolver.
As the "age old" adage goes, "it is always DNS".
For DNS stability, image security visability and other ilities, we've switched our base distribution to Ubuntu Slim. If Macho Man Randy Savage were still around, I'm sure he'd be glad for the change.
Upgrading to GA Release
The release of Helm Classic and RC2 have put in place the necessary functionality to provide an in-place upgrade story. The TL;DR version is that you will need Helm Classic 0.8.0 or later, a running Workflow RC2 cluster, a copy of your templated parameters and some cluster secrets. A quick un-install and re-install will bring your Workflow cluster up to stable when we ship our GA Release.
For the intrepid, you should be able to upgrade from beta4 to RC2 by manually applying a few Kubernetes annotations. Give it a shot! Your experience here is very welcome.
The updated documenatation is available here.
Upgrading from RC1 to RC2 should work as-documented.
Platform SSL Secret Changes
To mirror the secret format used by Ingress controllers in Kubernetes, we've changed the keys used for the platform SSL
certificate. Before upgrading, update the secret via
kubectl --namespace=deis edit secret deis-router-platform-cert:
- Copy the existing
cert key to
- copy the existing
key key (ahem) to
Once you have completed the upgrade to RC2 you may delete the
key keys (ahem).
That's not all!
Many bug fixes, small updates, little tweaks and tuning, our ride has been pimped and is ready for prime time.
Click through for the complete release notes for RC1 and RC2.