Release Notes and Known Issues

Red Hat Container Development Kit 2.0 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 Vagrantfile is provided (cdk/components/rhel/rhel-ose/Vagrantfile in the Red Hat Developer Tools ZIP file) that automatically provisions an OpenShift instance and sets it up for use in the Red Hat CDK Vagrant box, along with all other prerequisities, including the Docker service.

Red Hat Container Development Kit 2.0 offers a simple way to set up the Kubernetes container orchestration service (both in master and node modes) using a single command. A Vagrantfile is provided (cdk/components/rhel/misc/rhel-k8s-singlenode-setup/Vagrantfile in the Red Hat Developer Tools ZIP file) that provisions the Red Hat CDK Vagrant box to have the Kubernetes service and all other prerequisities, including the Docker service, ready for use.

The vagrant-service-manager plugin, included in version 1.0.1, provides for a way to configure the Red Hat CDK for different use cases. The plugin also displays information about services running within the Red Hat CDK box, thus providing an interface between Red Hat CDK and the host workstation. Users can utilize familiar tools, such as the Eclipse IDE, in their development environment of choice (Linux, Mac OS X, or Windows) to interact with the container services deployed in the Red Hat CDK box.

The vagrant-sshfs plugin, included in version 1.1.0, uses the SSHFS software to open a file-synchronization channel between the Red Hat CDK box and the host system. The solution works on all supported platforms (Linux, Mac OS X, Windows) and with both supported virtualization providers (KVM/libvirt, VirtualBox), and therefore provides a good alternative to other ways of synchronizing data (NFS, rsync, VirtualBox shared folders).

The vagrant-registration plugin, included in version 1.2.1, provides for an easy to way to register the Red Hat CDK Vagrant boxes, which are based on Red Hat Enterprise Linux, during their provisioning. The process can be automated by adding login credentials into a system-wide or box-specific Vagrantfile or by setting respective environment variables (SUB_USERNAME and SUB_PASSWORD).

Running an application using Kubernetes fails when a Kubernetes pod needs to use an emptyDir volume because a corresponding SELinux context is not automatically set for emptyDir.

Due to a bug in the vagrant-service-manager plugin, the vagrant service-manager env command reports that the Kubernetes service is stopped in the Red Hat CDK box even when it is running. To work around this issue, users can upgrade to the latest version of the vagrant-service-manager plugin from rubygems.org, in which the bug has been fixed. To upgrade, run the following command: vagrant plugin update vagrant-service-manager or install the newest version by running the following command: vagrant plugin install vagrant-service-manager.

Due to a bug in Atomic CLI, the command to run AtomicApp fails when issued with sudo as follows: sudo atomic run <atomicapp-docker-image>. To work around the problem, use sudo with the -E option: sudo -E atomic run <atomicapp-docker-image>.

Virtualbox is a supported virtualization provider for Red Hat CDK, but the Virtualbox Guest Additions software, which offers various drivers and applications and is useful for sharing folders between the Vagrant box and the host system, is not pre-installed in the Red Hat CDK box because its licence is not compatible with Red Hat CDK. Users are recommended to use SSHFS provided by the vagrant-sshfs plugin to enable Vagrant synchronized folders.

The Red Hat CDK Vagrant box for the Virtualbox virtualization provider does not come with the Virtualbox Guest Additions software pre-installed because of a licensing-incompatibity issue. Users who attempt to work around the absence of Virtualbox Guest Additions by installing the software using the vagrant-vbguest plugin are advised that it is not possible to use both the vagrant-vbguest and vagrant-registartion plugins together. If you wish to install either one of the plugins, make sure that the other one is not installed.

When the vagrant ssh command is used on Mac OS X to log into the Red Hat CDK Vagrant box, the following warning message is displayed:

bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory"

The message can be safely disregarded.

Internal network proxies, which are used for connecting to the Internet in some networking configurations, are not supported by Red Hat CDK.

While it is possible to start the OpenShift service in Red Hat CDK when the host system is not connected to the Internet, Internet connection is required for running applications using OpenShift because OpenShift needs to download required Docker-formatted container images for applications to function.

DNS addressing provided by the external xip.io service is unavailable without a working Internet connection.

Starting or restarting OpenShift takes more time than expected. The reason lies in the way the Red Hat CDK virtual machine is configured. The same problem occurs when running the vagrant service-manager restart openshift command or during initialization using the vagrant up command. This command may fail with a timeout error, even though the environment is running. It is only the OpenShift service that starts slowly.

The Vagrantfile for the rhel-k8s-singlenode-setup configuration does not support credentials stored in the system Vagrantfile. While storing user credentials in the system Vagrantfile works for registering an environment initialized using the rhel-ose configuration, for the rhel-k8s-singlenode-setup Vagranfile, the registration plugin asks for credentials interactively. This problem is caused by a bug in the Vagrantfile.

To work around the problem, delete the config.registration lines from the Vagrantfile, or copy this part from the rhel-ose Vagrantfile.