Container Development Kit

Updates

Red Hat Container Development Kit 3.7 (CDK 3.7)

December 2018

New features for this release are: 

  • Red Hat Container Development Kit 3.7 is based on Minishift 1.27.0, a command line tool to provision OpenShift and Kubernetes locally for application developers. 

  • CDK 3.7 now includes OpenShift Container Platform v3.11.14. This is the default container platform for this release. 

  • Uses the native system keychain for storing passwords

  • Improvements around timezone handling

  • A VM driver for hyperkit (--vm-driver hyperkit) 

  • Use of registry.redhat.io for handling authorization and connection

  • Technology Preview: This release includes a technology preview of a system tray icon for macOS and Windows. The icon appears the first time you run minishift, and it makes it easy to start and stop your minishift profiles. For example, on the Mac, the system tray icon looks like this: 

    The new CDK system tray icon on macOS

    In this example there are two profiles, Minishift and Faas-Tutorial-Nodejs. The Faas-Tutorial-Nodejs profile is currently running.

Red Hat Container Development Kit 3.6 (CDK 3.6)

October 2018

New features for this release are:

  • Red Hat Container Development Kit 3.6 is based on Minishift 1.24.0, a command line tool to provision OpenShift and Kubernetes locally for application developers.

  • Container Development Kit now can run a local proxy server to handle proxy issues. The local proxy server assists with the use of CDK in a proxy environment. For more information, see Local Proxy Server. This feature is a Technical Preview.

  • Usability improvements:

    • Container Development Kit now saves non-default flags given to the minishift start command to the persistent configuration. You are not required to explicitly save these settings. To disable this feature, run the following command:

      • $ minishift config set save-start-flags false

    • Container Development Kit now allows you to start CDK with the latest OpenShift Container Platform version using the following command:

      • $ minishift start --ocp-tag latest

    • The generic driver for CDK has been improved by performing all of the required steps to allow OpenShift to start on the remote RHEL 7 machine.

    • Container Development Kit add-ons are easier to manage with an improved way to express dependencies between add-ons.

 

Red Hat Container Development Kit 3.5 (CDK 3.5)

July 2018

New features for this release are:

  • The latest Red Hat OpenShift Container Platform is included, and it can be updated to newly released versions as they become available by using the minishift start --ocp-tag <version>  command.
  • You can run the CDK against an existing RHEL 7 remote machine.
  • SSHFS is the default method for sharing folders on your host machine with the container environment running inside of the VM.
  • A local DNS server is included to reduce dependency on nip.io and to more fully enable disconnected work.
  • CDK 3.5 is based on Minishift 1.21.0.

 

Red Hat Container Development Kit 3.4 (CDK 3.4)

April 2018

New features for this release are:

  • OpenShift Container Platform v3.9.14
  • Image caching is enabled by-default now for OpenShift container images.
  • HyperV users can assign a static IP to CDK
  • Users can force hypervisors (except KVM) to reuse the same IP address which was assigned during first CDK start. (Technical preview)
  • Hostfolder mount using SSHFS (Technical preview)
  • Other notable changes - CDK now uses overlay as the default storage driver instead of devicemapper.

 

Red Hat Container Development Kit 3.3 (CDK 3.3)

January 2018

New features for this release are:

  • Support for OpenShift Container Platform v3.7.14
  • general availability of the image caching feature so that now image caching uses OCI tools.
  • Improvements to profiles feature such as global caching for all profiles
  • Improved add-on feature

 

Red Hat Container Development Kit 3.2 (CDK 3.2)

November 2017

New features for this release are:

  • Supports OpenShift 3.6
  • Users can now create multiple Minishift instances
  • Users can assign a static IP to Minishift VM on HyperV (Technical preview)
  • Users receive a warning/error if they are trying to use a addon that is not supported with the applicable OpenShift version. Read about OpenShift addons.

 

Red Hat Container Development Kit 3.1 (CDK 3.1)

August 2017

New features for this release are:

  • Based on Minishift community release version 1.3.1
  • Local container image cache for OpenShift images
  • Improved capabilities for the add-ons feature
  • CDK RPM for DevSuite RHEL 7 installer
  • Requires: native hypervisor (Hyper-V/xhyve/KVM) or VirtualBox

 

Red Hat Container Development Kit 3 (CDK 3)

May 2017

Red Hat Container Development Kit 3.0 contains the Minishift tool, a Red Hat Enterprise Linux 7 ISO, and the oc binary for interacting with OpenShift Container Platform.

Minishift

Red Hat Container Development Kit 3.0 introduces Minishift, a new command-line tool to provision OpenShift locally for application developers to develop application for OpenShift. It supports all native hypervisors: libvirt/KVM on Red Hat Enterprise Linux, xhyve on macOS, Hyper-V on Microsoft Windows, or VirtualBox on all platforms.

Compared to Container Development Kit 2.x, CDK 3.0...

  • Provides a new single command-line tool, Minishift, for interacting with the Container Development EnvironmentIs easier and quicker to install
  • Has no dependency on Vagrant
  • Is only 400MB in size, which is 60% less than Container Development Kit 2.x
  • Has fewer components to install — just a single binary

Red Hat Container Development Kit 3.0 Highlights

  • Ability to use add-ons (experimental). See Minishift Add-ons.
  • The oc-env command for displaying how to configure your host shell for working with the OpenShift Container Platform instance provided by the Container Development Environment.
  • The docker-env command for displaying how to configure your host shell for working with the Docker instance provided by the Container Development Environment.
  • The config command for modifying Minishift configuration properties. With this command, users can change OpenShift master configuration.
  • A registry for Docker-formatted container images integrated in OpenShift for speeding up local development workflow.
  • Possibility to choose a specific OpenShift version to run using minishift start --openshift-version <version>.
  • A persistent OpenShift across Minishift stop and start.

 

Red Hat Container Development Kit 2.4 (CDK 2.4) is now available

February 2017

The following features were added with Red Hat Container Development Kit 2.4:

  • Supports the latest version of Red Hat OpenShift Container Platform (OCP 3.4.0.40)
  • Minor bug fixes.

Red Hat Container Development Kit 2.3 (CDK 2.3) is now available

December 2016

The following features are some of those added with Red Hat Container Development Kit 2.3:

  • Proxy Connections Are Supported both for HTTP and HTTPS - The Container Development Environment provided by Red Hat Container Development Kit 2.3 now supports connecting to the Internet through proxy servers — both HTTP and HTTPS configurations. This support is available to all services running within the Container Development Environment, including Openshift Enterprise, Kubernetes, and Docker.
  • Unified Vagrantfiles for All Hypervisors - Vagrantfiles distributed as a part of the Red Hat Container Tools ZIP file and used for initializing the Container Development Environment Vagrant box have been unified to work with all supported hypervisors. 
  • The Vagrant-service-manager Plugin Can Install Client Binaries for OpenShift, Docker, and Kubernetes - Client binaries for the user’s host system, which can be used to interact with services running inside the Container Development Environment, can now be installed using the Vagrant-service-manager' plugin.

Red Hat Container Development Kit 2.2 (CDK 2.2)

September 2016

The following features were added with Red Hat Container Development Kit 2.2:

  • Proxy Connections Are Supported both for HTTP and HTTPS - The Container Development Environment provided by CDK 2.2 now supports connecting to the Internet through proxy servers — both HTTP and HTTPS configurations. This is available to all services including Openshift Enterprise, Kubernetes, and Docker.
  • Unified Vagrantfiles for All Hypervisors - Vagrantfiles distributed as a part of the Red Hat Container Tools ZIP file have been unified to work with all supported hypervisors.
  • Vagrant-sshfs Plugin Is Now Used by Default JBoss Developer Studio - There is no longer a need for separate Vagrantfiles.
  • Vagrant-service-manager Plugin Can Install Client Binaries for OpenShift, Docker, and Kubernetes - Client binaries for the user’s host system, which can be used to interact with services running inside the Container Development Environment, can now be installed using the Vagrant-service-manager' plugin.

Red Hat Container Development Kit 2.1 (CDK 2.1)

June 2016

The new features offered by Red Hat Container Development Kit 2.1 include.

  • OpenShift Enterprise 3.2 - OpenShift Enterprise provided by the Container Development Environment has been upgraded to version 3.2. 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.
  • Hyper-V Tech Preview Added - A Container Development Kit Vagrant box is now available for the Hyper-V hypervisor on Microsoft Windows.
  • Reduced Size of Vagrant Boxes - The size of the Vagrant Boxes has been reduced by approximately 150 MB compared to Container Development Kit 2.0.
  • Persistent Volumes for Storing Data between Restarts - 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.
  • OpenShift Registry Available on Host System - 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.

Red Hat Container Development Kit 2 (CDK 2) is now available for beta testing!

December 2015

The beta release of the Red Hat Container Development Kit 2 enables developers to take advantage of pre-configured images and tools to accelerate the development of container-based applications that can be deployed across Red Hat’s portfolio of container hosts and platforms - including OpenShift Enterprise 3 - from the comfort of your own laptop.

New components in CDK 2 include:

  • Support for the Nulecule specification. What is Nulecule? Nulecule defines a pattern and model for packaging complex multi-container applications, referencing all their dependencies, including orchestration metadata in a container image for building, deploying, monitoring, and active management.
  • Atomic App - Red Hat’s reference implementation of the Nulecule Specification. It can be used to accelerate the development of container-based applications. Atomic App itself is packaged and is included as a container.
  • Image Factory (imagefactory-v2c) - a tool to accelerate the importing and conversion of disk images (e.g. virtual machine images) into Docker base images - complete with appropriate metadata.
  • Vagrant plug-in for Eclipse Docker Tooling - allows users to connect the Eclipse Docker tooling to the Docker daemon running in your CDK VM.
  • Hypervisor support includes Vagrantfiles for KVM, VirtualBox, and now with CDK 2, VMware.

Red Hat Software Collections are available as container images for use with the Red Hat Container Development Kit via the Red Hat Registry. Red Hat Software Collections are inclusive of the latest stable versions of web development tools, dynamic languages, and open source databases.

Create your own private container registry with available tools.

See the Get Started to make your way into Docker containers.

Red Hat introduces CDK for easy Docker app development

March 2015

The initial version of CDK was the first to set up a Docker container development environment for Windows, MacOS, and Linux. Supported hypervisors were Virtualbox and KVM. Given the latest enhancements, developers are encouraged to use the CDK 2 beta (above).