Update docs for v0.8.0 (#468)

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

Author: xmudrii

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+# [v0.8.0](https://github.com/kubermatic/kubeone/releases/tag/v0.8.0) - 2019-05-30
+
+## Added
+
+* Add support for VMware vSphere ([#428](https://github.com/kubermatic/kubeone/pull/428))
+
 # [v0.7.0](https://github.com/kubermatic/kubeone/releases/tag/v0.7.0) - 2019-05-28
 
 ## Added

README.md

@@ -38,7 +38,7 @@ upgrade to the v0.6.0 or newer as soon as possible.
   manage worker nodes
 * Integrates with Terraform for sourcing data about infrastructure and control
   plane nodes
-* Officially supports AWS, DigitalOcean, GCE, Hetzner, Packet and OpenStack
+* Officially supports AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack and VMware vSphere
 
 ## Installing KubeOne
 
@@ -53,8 +53,8 @@ expected.
 Alternatively, you can obtain KubeOne via [GitHub Releases][9]:
 
 ```bash
-curl -LO https://github.com/kubermatic/kubeone/releases/download/v0.7.0/kubeone_0.7.0_linux_amd64.zip
-unzip kubeone_0.7.0_linux_amd64.zip
+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
 sudo mv kubeone /usr/local/bin
 ```
 
@@ -80,10 +80,11 @@ In the following table you can find what are supported Kubernetes 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 | Supported providers                                |
-|-----------------|------|------|----------------------------------------------------|
-| v0.6.0+         | +    | +    | AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack |
-| v0.5.0          | +    | +    | AWS, DigitalOcean, GCE, Hetzner, OpenStack         |
+| KubeOne version | 1.14 | 1.13 | Supported providers                                         |
+|-----------------|------|------|-------------------------------------------------------------|
+| v0.8.0+         | +    | +    | AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack, vSphere |
+| v0.6.0+         | +    | +    | AWS, DigitalOcean, GCE, Hetzner, Packet, OpenStack          |
+| v0.5.0          | +    | +    | AWS, DigitalOcean, GCE, Hetzner, OpenStack                  |
 
 ## Getting Started
 

docs/environment_variables.md

@@ -35,4 +35,5 @@ In the following table you can find all configuration variables with support for
 | `VSPHERE_ADDRESS` | The address of the vSphere instance |
 | `VSPHERE_USERNAME` | The username of the vSphere user |
 | `VSPHERE_PASSWORD` | The password of the vSphere user |
+| | |
 | `GOOGLE_CREDENTIALS` | GCE Service Account |

docs/frequently_asked_questions.md

@@ -31,11 +31,11 @@ worker nodes, KubeOne and [Kubermatic machine-controller][4] need to support
 that provider.
 
 Currently we support AWS, DigitalOcean, Google Compute Engine (GCE), Hetzner,
-Packet and OpenStack.
+Packet, OpenStack and VMware vSphere.
 
 ## Are on-prem and bare metal clusters supported?
 
-Yes. We support OpenStack, with support for vSphere coming soon.
+Yes. We officially support VMware vSphere and OpenStack.
 
 ## Does KubeOne handles the infrastructure and cloud resources?
 

docs/quickstart-aws.md

@@ -2,13 +2,13 @@
 
 In this quick start we're going to show how to get started with KubeOne on AWS. We'll cover how to create the needed infrastructure using our example Terraform scripts and then install Kubernetes. Finally, we're going to show how to destroy the cluster along with the infrastructure.
 
-As a result, you'll get Kubernetes 1.14.1 High-Available (HA) clusters with three control plane nodes and two worker nodes.
+As a result, you'll get Kubernetes 1.14.2 High-Available (HA) clusters with three control plane nodes and two worker nodes.
 
 ### Prerequisites
 
 To follow this quick start, you'll need:
 
-* `kubeone` v0.7.0 or newer installed, which can be done by following the `Installing KubeOne` section of [the README](https://github.com/kubermatic/kubeone/blob/master/README.md),
+* `kubeone` v0.8.0 or newer installed, which can be done by following the `Installing KubeOne` section of [the README](https://github.com/kubermatic/kubeone/blob/master/README.md),
 * `terraform` v0.11 installed. The binaries for `terraform` can be found on the [Terraform website](https://www.terraform.io/downloads.html)
 
 **Note:** Due to breaking changes made in Terraform v0.12, it's currently not possible to use example Terraform scripts with Terraform v0.12.
@@ -100,14 +100,14 @@ Before you start you'll need a configuration file that defines how Kubernetes
 will be installed, e.g. what version will be used and what features will be
 enabled. For the configuration file reference run `kubeone config print --full`.
 
-To get started you can use the following configuration. It'll install Kubernetes 1.14.1 and create 3 worker nodes. KubeOne automatically populates all needed information about worker nodes from the [Terraform output](https://github.com/kubermatic/kubeone/blob/ec8bf305446ac22529e9683fd4ce3c9abf753d1e/examples/terraform/aws/output.tf#L38-L87). Alternatively, you can set those information manually. As KubeOne is using [Kubermatic `machine-controller`](https://github.com/kubermatic/machine-controller) for creating worker nodes, see [AWS example manifest](https://github.com/kubermatic/machine-controller/blob/master/examples/aws-machinedeployment.yaml) for available options.
+To get started you can use the following configuration. It'll install Kubernetes 1.14.2 and create 3 worker nodes. KubeOne automatically populates all needed information about worker nodes from the [Terraform output](https://github.com/kubermatic/kubeone/blob/ec8bf305446ac22529e9683fd4ce3c9abf753d1e/examples/terraform/aws/output.tf#L38-L87). Alternatively, you can set those information manually. As KubeOne is using [Kubermatic `machine-controller`](https://github.com/kubermatic/machine-controller) for creating worker nodes, see [AWS example manifest](https://github.com/kubermatic/machine-controller/blob/master/examples/aws-machinedeployment.yaml) for available options.
 
 ```yaml
 apiVersion: kubeone.io/v1alpha1
 kind: KubeOneCluster
 name: demo
 versions:
-  kubernetes: '1.14.1'
+  kubernetes: '1.14.2'
 cloudProvider:
   name: 'aws'
 ```
@@ -194,4 +194,4 @@ terraform destroy
 
 You'll be asked to enter `yes` to confirm your intention to destroy the cluster.
 
-Congratulations! You're now running Kubernetes 1.14.1 HA cluster with three control plane nodes and three worker nodes. If you want to learn more about KubeOne and its features, such as [upgrades](upgrading_cluster.md), make sure to check our [documentation](https://github.com/kubermatic/kubeone/tree/master/docs).
+Congratulations! You're now running Kubernetes 1.14.2 HA cluster with three control plane nodes and three worker nodes. If you want to learn more about KubeOne and its features, such as [upgrades](upgrading_cluster.md), make sure to check our [documentation](https://github.com/kubermatic/kubeone/tree/master/docs).

docs/quickstart-digitalocean.md

@@ -2,13 +2,13 @@
 
 In this quick start we're going to show how to get started with KubeOne on DigitalOcean. We'll cover how to create the needed infrastructure using our example Terraform scripts and then install Kubernetes. Finally, we're going to show how to destroy the cluster along with the infrastructure.
 
-As a result, you'll get Kubernetes 1.14.1 High-Available (HA) clusters with three control plane nodes and two worker nodes.
+As a result, you'll get Kubernetes 1.14.2 High-Available (HA) clusters with three control plane nodes and two worker nodes.
 
 ### Prerequisites
 
 To follow this quick start, you'll need:
 
-* `kubeone` v0.7.0 or newer installed, which can be done by following the `Installing KubeOne` section of [the README](https://github.com/kubermatic/kubeone/blob/master/README.md),
+* `kubeone` v0.8.0 or newer installed, which can be done by following the `Installing KubeOne` section of [the README](https://github.com/kubermatic/kubeone/blob/master/README.md),
 * `terraform` v0.11 installed. The binaries for `terraform` can be found on the [Terraform website](https://www.terraform.io/downloads.html)
 
 **Note:** Due to breaking changes made in Terraform v0.12, it's currently not possible to use example Terraform scripts with Terraform v0.12.
@@ -96,14 +96,14 @@ Before you start you'll need a configuration file that defines how Kubernetes
 will be installed, e.g. what version will be used and what features will be
 enabled. For the configuration file reference run `kubeone config print --full`.
 
-To get started you can use the following configuration. It'll install Kubernetes 1.14.1, create 3 worker nodes and deploy the [external cloud controller manager](https://github.com/digitalocean/digitalocean-cloud-controller-manager). The external cloud controller manager takes care of providing correct information about nodes from the DigitalOcean API and allows you to use the `type: LoadBalancer` services. KubeOne automatically populates information about the worker nodes from the [Terraform output](https://github.com/kubermatic/kubeone/blob/ec8bf305446ac22529e9683fd4ce3c9abf753d1e/examples/terraform/digitalocean/output.tf#L38-L59). Alternatively, you can set those information manually. As KubeOne is using [Kubermatic `machine-controller`](https://github.com/kubermatic/machine-controller) for creating worker nodes, see [DigitalOcean example manifest](https://github.com/kubermatic/machine-controller/blob/master/examples/digitalocean-machinedeployment.yaml) for available options.
+To get started you can use the following configuration. It'll install Kubernetes 1.14.2, create 3 worker nodes and deploy the [external cloud controller manager](https://github.com/digitalocean/digitalocean-cloud-controller-manager). The external cloud controller manager takes care of providing correct information about nodes from the DigitalOcean API and allows you to use the `type: LoadBalancer` services. KubeOne automatically populates information about the worker nodes from the [Terraform output](https://github.com/kubermatic/kubeone/blob/ec8bf305446ac22529e9683fd4ce3c9abf753d1e/examples/terraform/digitalocean/output.tf#L38-L59). Alternatively, you can set those information manually. As KubeOne is using [Kubermatic `machine-controller`](https://github.com/kubermatic/machine-controller) for creating worker nodes, see [DigitalOcean example manifest](https://github.com/kubermatic/machine-controller/blob/master/examples/digitalocean-machinedeployment.yaml) for available options.
 
 ```yaml
 apiVersion: kubeone.io/v1alpha1
 kind: KubeOneCluster
 name: demo
 versions:
-  kubernetes: '1.14.1'
+  kubernetes: '1.14.2'
 cloudProvider:
   name: 'digitalocean'
   external: true
@@ -193,4 +193,4 @@ terraform destroy
 
 You'll be asked to enter `yes` to confirm your intention to destroy the cluster.
 
-Congratulations! You're now running Kubernetes 1.14.1 HA cluster with three control plane nodes and three worker nodes. If you want to learn more about KubeOne and its features, such as [upgrades](upgrading_cluster.md), make sure to check our [documentation](https://github.com/kubermatic/kubeone/tree/master/docs).
+Congratulations! You're now running Kubernetes 1.14.2 HA cluster with three control plane nodes and three worker nodes. If you want to learn more about KubeOne and its features, such as [upgrades](upgrading_cluster.md), make sure to check our [documentation](https://github.com/kubermatic/kubeone/tree/master/docs).

docs/quickstart-gce.md

@@ -5,14 +5,14 @@ We'll cover how to create the needed infrastructure using our example terraform
 configuration and then install Kubernetes. Finally, we're going to show how to
 destroy the cluster along with the infrastructure.
 
-As a result, you'll get Kubernetes 1.14.1 High-Available (HA) clusters with
+As a result, you'll get Kubernetes 1.14.2 High-Available (HA) clusters with
 three control plane nodes and two worker nodes.
 
 ### Prerequisites
 
 To follow this quick start, you'll need:
 
-* `kubeone` v0.7.0 or newer installed, which can be done by following the `Installing KubeOne`
+* `kubeone` v0.8.0 or newer installed, which can be done by following the `Installing KubeOne`
   section of [the
   README](https://github.com/kubermatic/kubeone/blob/master/README.md),
 * `terraform` v0.11 installed. The binaries for `terraform` can be found on the
@@ -140,7 +140,7 @@ will be installed, e.g. what version will be used and what features will be
 enabled. For the configuration file reference run `kubeone config print --full`.
 
 To get started you can use the following configuration. It'll install Kubernetes
-1.14.1 and create 3 worker nodes. KubeOne automatically populates information
+1.14.2 and create 3 worker nodes. KubeOne automatically populates information
 about worker nodes from the [Terraform output](https://github.com/kubermatic/kubeone/blob/ec8bf305446ac22529e9683fd4ce3c9abf753d1e/examples/terraform/gce/output.tf#L41-L81).
 Alternatively, you can set those information manually. As KubeOne is using
 [Kubermatic
@@ -154,7 +154,7 @@ apiVersion: kubeone.io/v1alpha1
 kind: KubeOneCluster
 name: demo
 versions:
-  kubernetes: '1.14.1'
+  kubernetes: '1.14.2'
 cloudProvider:
   name: 'gce'
 ```
@@ -242,7 +242,7 @@ terraform destroy
 
 You'll be asked to enter `yes` to confirm your intention to destroy the cluster.
 
-Congratulations! You're now running Kubernetes 1.14.1 HA cluster with three
+Congratulations! You're now running Kubernetes 1.14.2 HA cluster with three
 control plane nodes and three worker nodes. If you want to learn more about
 KubeOne and its features, such as [upgrades](upgrading_cluster.md), make sure to
 check our

docs/quickstart-hetzner.md

@@ -2,13 +2,13 @@
 
 In this quick start we're going to show how to get started with KubeOne on Hetzner. We'll cover how to create the needed infrastructure using our example Terraform scripts and then install Kubernetes. Finally, we're going to show how to destroy the cluster along with the infrastructure.
 
-As a result, you'll get Kubernetes 1.14.1 High-Available (HA) clusters with three control plane nodes and three worker nodes.
+As a result, you'll get Kubernetes 1.14.2 High-Available (HA) clusters with three control plane nodes and three worker nodes.
 
 ### Prerequisites
 
 To follow this quick start, you'll need:
 
-* `kubeone` v0.7.0 or newer installed, which can be done by following the `Installing KubeOne` section of [the README](https://github.com/kubermatic/kubeone/blob/master/README.md),
+* `kubeone` v0.8.0 or newer installed, which can be done by following the `Installing KubeOne` section of [the README](https://github.com/kubermatic/kubeone/blob/master/README.md),
 * `terraform` v0.11 installed. The binaries for `terraform` can be found on the [Terraform website](https://www.terraform.io/downloads.html)
 
 **Note:** Due to breaking changes made in Terraform v0.12, it's currently not possible to use example Terraform scripts with Terraform v0.12.
@@ -90,14 +90,14 @@ Before you start you'll need a configuration file that defines how Kubernetes
 will be installed, e.g. what version will be used and what features will be
 enabled. For the configuration file reference run `kubeone config print --full`.
 
-To get started you can use the following configuration. It'll install Kubernetes 1.14.1, create 3 worker nodes and deploy the [external cloud controller manager](https://github.com/hetznercloud/hcloud-cloud-controller-manager). The external cloud controller manager takes care of providing correct information about the nodes. KubeOne automatically populates all needed information about worker nodes from the [Terraform output](https://github.com/kubermatic/kubeone/blob/a874fd5913ca2a86c3b8136982c2a00e835c2f62/examples/terraform/hetzner/output.tf#L26-L36). Alternatively, you can set those information manually. As KubeOne is using [Kubermatic `machine-controller`](https://github.com/kubermatic/machine-controller) for creating worker nodes see [Hetzner example manifest](https://github.com/kubermatic/machine-controller/blob/master/examples/hetzner-machinedeployment.yaml) for available options.
+To get started you can use the following configuration. It'll install Kubernetes 1.14.2, create 3 worker nodes and deploy the [external cloud controller manager](https://github.com/hetznercloud/hcloud-cloud-controller-manager). The external cloud controller manager takes care of providing correct information about the nodes. KubeOne automatically populates all needed information about worker nodes from the [Terraform output](https://github.com/kubermatic/kubeone/blob/a874fd5913ca2a86c3b8136982c2a00e835c2f62/examples/terraform/hetzner/output.tf#L26-L36). Alternatively, you can set those information manually. As KubeOne is using [Kubermatic `machine-controller`](https://github.com/kubermatic/machine-controller) for creating worker nodes see [Hetzner example manifest](https://github.com/kubermatic/machine-controller/blob/master/examples/hetzner-machinedeployment.yaml) for available options.
 
 ```yaml
 apiVersion: kubeone.io/v1alpha1
 kind: KubeOneCluster
 name: demo
 versions:
-  kubernetes: '1.14.1'
+  kubernetes: '1.14.2'
 cloudProvider:
   name: 'hetzner'
   external: true
@@ -185,4 +185,4 @@ terraform destroy
 
 You'll be asked to enter `yes` to confirm your intention to destroy the cluster.
 
-Congratulations! You're now running Kubernetes 1.14.1 HA cluster with three control plane nodes and three worker nodes. If you want to learn more about KubeOne and its features, such as [upgrades](upgrading_cluster.md), make sure to check our [documentation](https://github.com/kubermatic/kubeone/tree/master/docs).
+Congratulations! You're now running Kubernetes 1.14.2 HA cluster with three control plane nodes and three worker nodes. If you want to learn more about KubeOne and its features, such as [upgrades](upgrading_cluster.md), make sure to check our [documentation](https://github.com/kubermatic/kubeone/tree/master/docs).