Release notes: AWS Quick Start for Kubernetes by Heptio

The Quick Start builds Kubernetes 1.8.2.


Release date: 10-26-2017

The Quickstart now includes a default StorageClass, to support dynamic provisioning of PersistentVolume objects. These PersistentVolumes are frequently required by Helm charts, including the Wordpress Chart. For more information about the StorageClass and PersistentVolume objects, see the documentation.

Since we last updated these release notes, we’ve provided several updates to the QuickStart itself. Here’s a summary of things to be aware of:

  • Kubernetes 1.8.1 introduced a number of new features and enhancements:

    • Changes to group and version for a number of APIs, including the workloads, metrics, and auditing APIs.
    • Additional flags and commands for kubectl. Note especially the new RBAC reconcile command kubectl auth reconcile -f <FILE>.

    For details, see the 1.8 release notes.

  • Kubernetes 1.7 is a milestone release that adds features for security, stateful application, and extensibility, motivated by widespread production use of Kubernetes. For details, see the 1.7 release notes. Version 1.7.6, the previous version of the Heptio QuickStart, included numerous bugfixes.

Note:Make sure to update your kubectl client to the version of your Kubernetes server. If you update to version 1.8, make sure to check the release notes for breaking changes.


Release date: 5-25-2017

Kubernetes 1.6.4 is a bugfix release. No significant changes in behavior are expected between this version and v1.6.2.

For a full description of the bug fixes since v1.6.2, see the Kubernetes release notes:


Release date: 4-27-2017

Kubernetes 1.6.2 is the first Quick Start update for the 1.6 minor point release. Do not expect the Kubernetes universe to be caught up. Things that worked on 1.5.x may be broken now, mostly because of the new RBAC feature. You can run 1.6 without it, but in order to build a more secure cluster, this Quick Start enables RBAC.

Update kubectl client

To get the most out of a 1.6 cluster, you should use kubectl to manage your cluster(s). You should update the kubectl client to 1.6.2.

For all operating systems and general info, please refer to Installing and Setting Up kubectl in Docker’s documentation.

Commands to update and verify your local kubectl client on OS X:

curl -LO$(curl -s
chmod +x ./kubectl
sudo mv ./kubectl /usr/local/bin/kubectl
kubectl version

Or, if you installed kubectl with Homebrew:

brew upgrade kubectl

The Client Version line from your output should refer to 1.6.2 now:

Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.2",

Update Helm client

If you use Helm to install and manage applications on Kubernetes, you should update to the latest version (2.3.1).

For all operating systems and general info, please refer to Installing Helm.

Commands to update and verify your local Helm client on OS X:

curl -LO
tar -xvzf helm-v2.3.1-darwin-amd64.tar.gz
mv -f darwin-amd64/helm /usr/local/bin/helm
helm version

The Client Version line from your output should refer to 2.3.1 now:

Client: &version.Version{SemVer:"v2.3.1", GitCommit:"32562a3040bb5ca690339b9840b6f60f8ce25da4", GitTreeState:"clean"}

You can upgrade Tiller, the helm server side component, with:

helm init --upgrade

For more about the latest Helm release, please read Helm’s release notes.

Feature: RBAC

Kubernetes 1.6 expands support for role-based access control (RBAC) and this Quick Start now enables it by default. For information, see Using RBAC Authorization.

Different accounts that authenticate to the Kubernetes cluster now have different permission levels.

The kubeconfig file you download after running the Quick Start will still have full admin (“root”) access, so all our recommended next steps for the Quick Start work, because they use kubectl commands based on that kubeconfig.

However, other components of the Kubernetes ecosystem that use service accounts, like Helm, need to support RBAC before they will work. This means you may need to open up permissions on your system.

Read our RBAC article, How to: RBAC best practices and workarounds.