Prepare for the release v0.9.0 (#504)

* Update README.md

* Make install steps version-agnostic
* Recommend using officially released versions over running
of the master branch
* Mention that support for package managers is work in progress
* Add support for Kubernetes 1.15 to the compatibility table
* Minor updates and preparation for v0.9

Signed-off-by: Marko Mudrinić <[email protected]>

* Update the release process document

Signed-off-by: Marko Mudrinić <[email protected]>

* Add changelog for release v0.9.0

Signed-off-by: Marko Mudrinić <[email protected]>

* Add #508 to the changelog

Signed-off-by: Marko Mudrinić <[email protected]>

* Add #486 to the changelog

Signed-off-by: Marko Mudrinić <[email protected]>

* Update CHANGELOG.md with recent changes

Signed-off-by: Marko Mudrinić <[email protected]>

* Minor README improvements

Signed-off-by: Marko Mudrinić <[email protected]>

* Revert NodeLocalDNSCache

Signed-off-by: Marko Mudrinić <[email protected]>

* Change v0.9 release date in changelog

Signed-off-by: Marko Mudrinić <[email protected]>

Author: xmudrii

CHANGELOG.md

@@ -1,5 +1,43 @@
 # Changelog
 
+# [v0.9.0](https://github.com/kubermatic/kubeone/releases/tag/v0.9.0) - 2019-07-02
+
+## Action Required
+
+* The Terraform integration now requires Terraform v0.12+
+  * Please see the official [Upgrading to Terraform v0.12](https://www.terraform.io/upgrade-guides/0-12.html)
+  document to find out how to update your Terraform scripts for v0.12
+  * The example Terraform scripts coming with KubeOne are already updated for v0.12
+  * KubeOne is not able to parse output of `terraform output` generated with Terraform
+  v0.11 or older anymore
+  * The Terraform output template (`output.tf`) has been changed and KubeOne is not able
+  to parse the old template anymore. You can check the output template
+  used by [example Terraform scripts](https://github.com/kubermatic/kubeone/blob/986b4bc361c6a0ae5d5319990c54e82c15a66cb3/examples/terraform/aws/output.tf) as a
+  reference
+
+## Added
+
+* Add support for Kubernetes 1.15 ([#486](https://github.com/kubermatic/kubeone/pull/486))
+* Add support for Microsoft Azure ([#469](https://github.com/kubermatic/kubeone/pull/469))
+* Add `kubeone completion` command for generating the shell completion scripts for `bash` and `zsh` ([#484](https://github.com/kubermatic/kubeone/pull/484))
+* Add `kubeone document` command for generating man pages and KubeOne documentation ([#484](https://github.com/kubermatic/kubeone/pull/484))
+* Add support for reading Terraform output directly from the directory ([#495](https://github.com/kubermatic/kubeone/pull/495))
+* Add missing fields to the workers specification API ([#499](https://github.com/kubermatic/kubeone/pull/499))
+
+## Changed
+
+* [BREAKING] KubeOne Terraform integration now uses Terraform v0.12+ ([#466](https://github.com/kubermatic/kubeone/pull/466))
+* [BREAKING] Change Terraform output template to conform with the KubeOneCluster API ([#503](https://github.com/kubermatic/kubeone/pull/503))
+* Fix Docker not starting properly for some providers on Ubuntu ([#512](https://github.com/kubermatic/kubeone/pull/512))
+* Fix `kubeone reset` failing if a MachineSet or Machine object has been already deleted and include more details in the error messages ([#508](https://github.com/kubermatic/kubeone/pull/508))
+* Fix ability to read Terraform output from the standard input (`stdin`) ([#479](https://github.com/kubermatic/kubeone/pull/479))
+* Update `machine-controller` to v1.3.0 ([#499](https://github.com/kubermatic/kubeone/pull/499))
+* Update DigitalOcean Cloud Controller Manager to v0.1.15 ([#516](https://github.com/kubermatic/kubeone/pull/516))
+* Use Docker 18.09.7 when provisioning new clusters ([#517](https://github.com/kubermatic/kubeone/pull/517))
+* Configure proxy for `kubelet` on control plane nodes if proxy settings are provided ([#496](https://github.com/kubermatic/kubeone/pull/496))
+* Configure proxy on worker nodes if proxy settings are provided ([#490](https://github.com/kubermatic/kubeone/pull/490))
+* Make GoBetween Load balancer configuration script work on all operating systems and fix minor bugs ([#494](https://github.com/kubermatic/kubeone/pull/494))
+
 # [v0.8.0](https://github.com/kubermatic/kubeone/releases/tag/v0.8.0) - 2019-05-30
 
 ## Added

README.md

@@ -45,35 +45,78 @@ upgrade to the v0.6.0 or newer as soon as possible.
 
 ## Installing KubeOne
 
-The easiest way to install KubeOne is using `go get`:
+### Downloading a binary from GitHub Releases
+
+The recommended way to obtain KubeOne is to grab the
+binary from the [GitHub Releases][9] page. On the
+releases page, find the binary for your operating system
+and architecture and download it or grab the URL and use
+`wget` or `curl` to download the binary.
+
 ```bash
-go get -u github.com/kubermatic/kubeone
+curl -LO https://github.com/kubermatic/kubeone/releases/download/v<version>/kubeone_<version>_linux_amd64.zip
 ```
-However, running of the master branch introduces potential risks as the project
-is currently in the alpha phase and backwards incompatible changes can be
-expected.
 
-Alternatively, you can obtain KubeOne via [GitHub Releases][9]:
+Extract the binary. On Linux and macOS, you can use `unzip`.
 
 ```bash
-curl -LO https://github.com/kubermatic/kubeone/releases/download/v0.8.0/kubeone_0.8.0_linux_amd64.zip
 unzip kubeone_0.8.0_linux_amd64.zip
+```
+
+Move the `kubeone` binary to your path, so you can easily
+invoke it from your terminal.
+
+```bash
 sudo mv kubeone /usr/local/bin
 ```
 
-If you already have KubeOne repository cloned, you can use Makefile to install
-KubeOne.
+### Building KubeOne
+
+The alternative way to install KubeOne is using `go get`.
+
+```bash
+go get -u github.com/kubermatic/kubeone
+```
+
+While running of the master branch is a great way to peak at and test
+the new features before they are released, note that master branch can
+break at any time or may contain bugs. Official releases are considered
+stable and recommended for the production usage.
+
+If you already have KubeOne repository cloned, you can use `make`
+to install it.
 
 ```bash
 make install
 ```
 
-To install completions for bash (zsh also available), run or put this command into your .bashrc file:
+### Using package managers
+
+Support for packages managers is still work in progress and expected
+to be finished for one of the upcoming release. For details about the
+progress follow the [issue #471][17]
+
+### Shell completion and generating documentation
+
+KubeOne comes with commands for generating scripts for the shell
+completion and for the documentation in format of man pages
+and more.
+
+To activate completions for `bash` (or `zsh`), run or put this command
+into your `.bashrc` file:
+
 ```bash
 . <(kubeone completion bash)
 ```
 
+To put changes in the effect, source your `.bashrc` file.
+
+```bash
+source ~/.bashrc
+```
+
 To generate documentation (man pages for example, more available), run:
+
 ```bash
 kubeone document man -o /tmp/man
 ```
@@ -96,12 +139,12 @@ In the following table you can find what are supported Kubernetes and Terraform
 versions for each KubeOne version. KubeOne versions that are crossed out are not
 supported. It's highly recommended to use the latest version whenever possible.
 
-| KubeOne version | 1.14 | 1.13 | Terraform | Supported providers                                                |
-|-----------------|------|------|-----------|--------------------------------------------------------------------|
-| v0.9.0+         | +    | +    | v0.12+    | AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack, vSphere, Azure |
-| v0.8.0+         | +    | +    | v0.11     | AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack, vSphere        |
-| v0.6.0+         | +    | +    | v0.11     | AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack                 |
-| v0.5.0          | +    | +    | v0.11     | AWS, DigitalOcean, GCE, Hetzner, OpenStack                         |
+| KubeOne version | 1.15 | 1.14 | 1.13 | Terraform | Supported providers                                                |
+|-----------------|------|------|------|-----------|--------------------------------------------------------------------|
+| v0.9.0+         | +    | +    | +    | v0.12+    | AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack, vSphere, Azure |
+| v0.8.0+         | -    | +    | +    | v0.11     | AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack, vSphere        |
+| v0.6.0+         | -    | +    | +    | v0.11     | AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack                 |
+| v0.5.0          | -    | +    | +    | v0.11     | AWS, DigitalOcean, GCE, Hetzner, OpenStack                         |
 
 ## Getting Started
 
@@ -168,3 +211,4 @@ See [the list of releases][3] to find out about feature changes.
 [14]: https://groups.google.com/forum/#!forum/loodse-dev
 [15]: http://slack.kubermatic.io/
 [16]: https://github.com/kubermatic/kubeone/blob/master/CONTRIBUTING.md#reporting-a-security-vulnerability
+[17]: https://github.com/kubermatic/kubeone/issues/471

docs/release_process.md

@@ -27,11 +27,9 @@ to reference to the upcoming version and generate a changelog.
 
 You need to update the following documents to point to the new release:
 
-* `README.md`
-  * Links and binary name should point to the upcoming version in the
-  [Installing KubeOne section][4]
-  * [Kubernetes versions compatibility section][5] if there are changes
-  in supported Kubernetes versions, Terraform versions and/or providers
+* The [Kubernetes versions compatibility][5] section of the
+`README.md` file should be updated if there are changes in supported
+Kubernetes versions, Terraform versions and/or providers
 * [Optional] Update [the quickstart guides][6] to require/recommend
 the latest version