Chapter 2. Release Notes

OpenShift Enterprise provided by the Container Development Environment has been upgraded to version 3.2. See the OpenShift Enterprise 3.2 Release Notes for information about new features in this version.

Red Hat Container Development Kit 2.1 offers a simple way to set up the OpenShift Enterprise Platform as a Service (PaaS), which extends the functionality of the Docker service and the Kubernetes container orchestration tool to provide a powerful and easy-to-use platform for building, deploying, and orchestrating multi-container applications and services.

A Container Development Kit Vagrant box is now available for the Hyper-V hypervisor on Microsoft Windows. Users can now set up Container Development Kit using the Hyper-V provider in Vagrant. Hyper-V is the native hypervisor in Microsoft Windows. Note that Hyper-V support is provided as Technology Preview in Red Hat Container Development Kit 2.1.

In Red Hat Container Development Kit 2.1, the size of the Vagrant Boxes has been reduced by approximately 150 MB compared to Container Development Kit 2.0.

Users can now use persistent volumes in order to preserve data between restarts of pods, OpenShift, or even the whole virtual machine that provides the Container Development Environment.

Users can now use the internal container-image registry provided by OpenShift as a stand-alone registry for docker-formatted container images on the host workstation.

Previously, the vagrant-service-manager plugin did report the status of services running within the Container Development Environment properly. With this update, a new command, status, has been added, which reports the status of required services. To use the new command, run:

vagrant service-manager status [service]

$ vagrant service-manager status [service]

Substitute [service] for the service you wish to learn about: docker, kubernetes, or openshift. When used without any argument, the command lists all services and their status.

Previously, a bug in the vagrant-registration plugin prevented the automatic installation of VirtualBox Guest Additions. The bug has been fixed, and the vagrant-vbguest plugin can now be used together with the vagrant-registration plugin to install VirtualBox Guest Additions in the Container Development Kit virtual machine.

Previously, provisioning of Vagrant boxes ran only once — during the first launch of a Vagrant box using the vagrant up command after the last vagrant destroy, unless the --provision flag was used. With the latest Container Development Kit Vagrantfiles, provisioning runs with every vagrant up.