From d18fa439e6be76232bd7dd7707768385dfc764cc Mon Sep 17 00:00:00 2001 From: Matthew Fisher Date: Thu, 1 Nov 2018 08:35:20 -0700 Subject: [PATCH 1/3] add s390x architecture to the release notes (#4741) Signed-off-by: Matthew Fisher --- docs/release_checklist.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/release_checklist.md b/docs/release_checklist.md index 3d48e2a44..58257a94a 100644 --- a/docs/release_checklist.md +++ b/docs/release_checklist.md @@ -236,6 +236,7 @@ Download Helm X.Y. The common platform binaries are here: - [Linux arm64](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-linux-arm64.tar.gz) ([checksum](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-linux-arm64.tar.gz.sha256)) - [Linux i386](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-linux-386.tar.gz) ([checksum](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-linux-386.tar.gz.sha256)) - [Linux ppc64le](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-linux-ppc64le.tar.gz) ([checksum](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-linux-ppc64le.tar.gz.sha256)) +- [Linux s390x](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-linux-s390x.tar.gz) ([checksum](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-linux-s390x.tar.gz.sha256)) - [Windows amd64](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-windows-amd64.zip) ([checksum](https://storage.googleapis.com/kubernetes-helm/helm-vX.Y.Z-windows-amd64.zip.sha256)) Once you have the client installed, upgrade Tiller with `helm init --upgrade`. From 8442851a5c566a01d9b4c69b368d64daa04f6a7f Mon Sep 17 00:00:00 2001 From: Matthew Fisher Date: Thu, 1 Nov 2018 08:36:03 -0700 Subject: [PATCH 2/3] docs(release_checklist): fix changelog generation command (#4694) Signed-off-by: Matthew Fisher --- docs/release_checklist.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release_checklist.md b/docs/release_checklist.md index 58257a94a..9213b4c1f 100644 --- a/docs/release_checklist.md +++ b/docs/release_checklist.md @@ -258,7 +258,7 @@ The changelog at the bottom of the release notes can be generated with this comm ```shell PREVIOUS_RELEASE=vX.Y.Z -git log --no-merges --pretty=format:'- %s %H (%aN)' $RELEASE_NAME $PREVIOUS_RELEASE +git log --no-merges --pretty=format:'- %s %H (%aN)' $PREVIOUS_RELEASE..$RELEASE_NAME ``` Once finished, go into GitHub and edit the release notes for the tagged release with the notes written here. From c60abb4dd051ac59375335cc6bc9476e73eecf02 Mon Sep 17 00:00:00 2001 From: Matthew Fisher Date: Thu, 1 Nov 2018 10:17:46 -0700 Subject: [PATCH 3/3] add special note for RBAC users (#4597) Signed-off-by: Matthew Fisher --- docs/install.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/install.md b/docs/install.md index 96d9bc9f7..e0e3db56d 100755 --- a/docs/install.md +++ b/docs/install.md @@ -113,6 +113,12 @@ Tiller, the server portion of Helm, typically runs inside of your Kubernetes cluster. But for development, it can also be run locally, and configured to talk to a remote Kubernetes cluster. +### Special Note for RBAC Users + +Most cloud providers enable a feature called Role-Based Access Control - RBAC for short. If your cloud provider enables this feature, you will need to create a service account for Tiller with the right roles and permissions to access resources. + +Check the [Kubernetes Distribution Guide](kubernetes_distros.md) to see if there's any further points of interest on using Helm with your cloud provider. Also check out the guide on [Tiller and Role-Based Access Control](rbac.md) for more information on how to run Tiller in an RBAC-enabled Kubernetes cluster. + ### Easy In-Cluster Installation The easiest way to install `tiller` into the cluster is simply to run