Update links to docs to v1.6 docs (#2704)

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

Author: kubermatic-bot

CHANGELOG/CHANGELOG-1.6.md

@@ -9,10 +9,10 @@ consult the changelog below before upgrading to this minor release.
 
 ### (No, really, you MUST read this before you upgrade)
 
-- The minimum Kubernetes version is increased to v1.24.0. Please use KubeOne 1.5 to upgrade your clusters to Kubernetes 1.24 prior to upgrading to KubeOne 1.6. If your clusters are running Docker, please [migrate them to containerd using KubeOne 1.5](https://docs.kubermatic.com/kubeone/main/guides/containerd-migration/). ([#2599](https://github.com/kubermatic/kubeone/pull/2599), [@xmudrii](https://github.com/xmudrii))
+- The minimum Kubernetes version is increased to v1.24.0. Please use KubeOne 1.5 to upgrade your clusters to Kubernetes 1.24 prior to upgrading to KubeOne 1.6. If your clusters are running Docker, please [migrate them to containerd using KubeOne 1.5](https://docs.kubermatic.com/kubeone/v1.6/guides/containerd-migration/). ([#2599](https://github.com/kubermatic/kubeone/pull/2599), [@xmudrii](https://github.com/xmudrii))
 - Stop applying `node-role.kubernetes.io/master` taint for Kubernetes 1.25+ nodes. The taint will be removed from existing nodes upon upgrading to Kubernetes 1.25. The KubeOneCluster API validation will reject hosts/nodes that have the `node-role.kubernetes.io/master` taint if the Kubernetes version is 1.25 or newer. `kubeone apply` will fail if you have nodes with the `node-role.kubernetes.io/master` taint running Kubernetes 1.25+ ([#2604](https://github.com/kubermatic/kubeone/pull/2604), [#2688](https://github.com/kubermatic/kubeone/pull/2688), [#2689](https://github.com/kubermatic/kubeone/pull/2689), [@xmudrii](https://github.com/xmudrii))
-- External CCM/CSI is required for vSphere clusters starting with Kubernetes 1.25. If your vSphere clusters are using the in-tree cloud provider (`.cloudProvider.external` is `false` or unset), you must migrate your vSphere clusters to the external CCM/CSI before upgrading to Kubernetes 1.25. Please check [the documentation for more details about the CCM/CSI migration](https://docs.kubermatic.com/kubeone/main/guides/ccm-csi-migration/). This change is introduced because vSphere requires the CSI driver to be deployed starting with Kubernetes 1.25 ([#2697](https://github.com/kubermatic/kubeone/pull/2697), [@xmudrii](https://github.com/xmudrii))
-- Forbid Kubernetes 1.26 and newer for OpenStack clusters with the in-tree cloud provider. The in-tree cloud provider for OpenStack is removed with Kubernetes 1.26.0. Make sure to [migrate to the external CCM/CSI](https://docs.kubermatic.com/kubeone/main/guides/ccm-csi-migration/) before upgrading to Kubernetes 1.26. ([#2573](https://github.com/kubermatic/kubeone/pull/2573), [@xmudrii](https://github.com/xmudrii))
+- External CCM/CSI is required for vSphere clusters starting with Kubernetes 1.25. If your vSphere clusters are using the in-tree cloud provider (`.cloudProvider.external` is `false` or unset), you must migrate your vSphere clusters to the external CCM/CSI before upgrading to Kubernetes 1.25. Please check [the documentation for more details about the CCM/CSI migration](https://docs.kubermatic.com/kubeone/v1.6/guides/ccm-csi-migration/). This change is introduced because vSphere requires the CSI driver to be deployed starting with Kubernetes 1.25 ([#2697](https://github.com/kubermatic/kubeone/pull/2697), [@xmudrii](https://github.com/xmudrii))
+- Forbid Kubernetes 1.26 and newer for OpenStack clusters with the in-tree cloud provider. The in-tree cloud provider for OpenStack is removed with Kubernetes 1.26.0. Make sure to [migrate to the external CCM/CSI](https://docs.kubermatic.com/kubeone/v1.6/guides/ccm-csi-migration/) before upgrading to Kubernetes 1.26. ([#2573](https://github.com/kubermatic/kubeone/pull/2573), [@xmudrii](https://github.com/xmudrii))
 - Add support for Ubuntu 22.04. Example Terraform configs for all providers are now using Ubuntu 22.04 by default. If you're using the latest Terraform configs with an existing cluster, make sure to bind the operating system/image to the image that you're currently using, otherwise your instances will get recreated ([#2367](https://github.com/kubermatic/kubeone/pull/2367), [@ahmedwaleedmalik](https://github.com/ahmedwaleedmalik))
 - `control_plane_replicas` variable in Terraform configs for Hetzner is renamed to `control_plane_vm_count`. If you set the old variable explicitly, make sure to migrate to the new variable before migrating to the new configs ([#2550](https://github.com/kubermatic/kubeone/pull/2550), [@xmudrii](https://github.com/xmudrii))
 - Forbid PodSecurityPolicy feature for Kubernetes clusters running 1.25 and newer. PodSecurityPolicies got removed from Kubernetes in 1.25. For more details, see [the official blog post](https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/) ([#2594](https://github.com/kubermatic/kubeone/pull/2594), [@xmudrii](https://github.com/xmudrii))

README.md

@@ -116,11 +116,11 @@ See [the list of releases][changelog] to find out about feature changes.
 [machine-controller]: https://github.com/kubermatic/machine-controller
 [operating-system-manager]: https://github.com/kubermatic/operating-system-manager
 [docs]: https://docs.kubermatic.com/kubeone/
-[docs-architecture]: https://docs.kubermatic.com/kubeone/main/architecture/
-[docs-concepts]: https://docs.kubermatic.com/kubeone/main/architecture/concepts/
-[docs-compatibility]: https://docs.kubermatic.com/kubeone/main/architecture/compatibility/
-[docs-getting-kubeone]: https://docs.kubermatic.com/kubeone/main/getting-kubeone/
-[docs-provisioning]: https://docs.kubermatic.com/kubeone/main/tutorials/creating-clusters/
+[docs-architecture]: https://docs.kubermatic.com/kubeone/v1.6/architecture/
+[docs-concepts]: https://docs.kubermatic.com/kubeone/v1.6/architecture/concepts/
+[docs-compatibility]: https://docs.kubermatic.com/kubeone/v1.6/architecture/compatibility/
+[docs-getting-kubeone]: https://docs.kubermatic.com/kubeone/v1.6/getting-kubeone/
+[docs-provisioning]: https://docs.kubermatic.com/kubeone/v1.6/tutorials/creating-clusters/
 [contributing-guide]: https://github.com/kubermatic/kubeone/blob/main/CONTRIBUTING.md
 [k8s-slack-kubeone]: https://kubernetes.slack.com/messages/CNEV2UMT7
 [k8s-slack]: http://slack.k8s.io/

addons/README.md

@@ -7,6 +7,6 @@ how to use the KubeOne Addons, consider the [KubeOne documentation][addons-docs]
 
 * [Cluster backups (with Restic)][backups-addon]
 
-[addons-docs]: (https://docs.kubermatic.com/kubeone/main/guides/addons/)
+[addons-docs]: (https://docs.kubermatic.com/kubeone/v1.6/guides/addons/)
 [backups-addon]: (./backups-restic)
 [restic]: (https://restic.net/)

addons/calico-vxlan/README.md

@@ -48,4 +48,4 @@ addons:
       MTU: 1400 # custom MTU
 ```
 
-[addon_params]: https://docs.kubermatic.com/kubeone/main/guides/addons/#parameters
+[addon_params]: https://docs.kubermatic.com/kubeone/v1.6/guides/addons/#parameters

addons/cluster-autoscaler/README.md

@@ -115,8 +115,8 @@ You can find more information about deploying addons in the
 [addon]: ./cluster-autoscaler.yaml
 [autoscaler]: https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler
 [machine-controller]: https://github.com/kubermatic/machine-controller
-[docs-concepts]: https://docs.kubermatic.com/kubeone/main/architecture/concepts/
-[docs-machinedeployment]: https://docs.kubermatic.com/kubeone/main/architecture/concepts/#machinedeployments
+[docs-concepts]: https://docs.kubermatic.com/kubeone/v1.6/architecture/concepts/
+[docs-machinedeployment]: https://docs.kubermatic.com/kubeone/v1.6/architecture/concepts/#machinedeployments
 [recommended-autoscaler-versions]: https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#releases
 [autoscaler-releases]: https://github.com/kubernetes/autoscaler/releases
-[using-addons]: https://docs.kubermatic.com/kubeone/main/guides/addons/
+[using-addons]: https://docs.kubermatic.com/kubeone/v1.6/guides/addons/

addons/cni-cilium/README.md

@@ -6,7 +6,7 @@ This addon is used to deploy [Cilium CNI](https://cilium.io/).
 
 This section what [addon parameters][params] can be used with this addon.
 
-[params]: https://docs.kubermatic.com/kubeone/main/guides/addons/#parameters
+[params]: https://docs.kubermatic.com/kubeone/v1.6/guides/addons/#parameters
 
 * `HubbleUI` - used to enable/disable Hubble UI listening on an IPv6 interface
   * `true` (default): enable listening on IPv6

docs/README.md

@@ -2,7 +2,7 @@
 
 ## User Documentation
 
-KubeOne user documentation can be found at [KubeOne docs website](https://docs.kubermatic.com/kubeone/main/)
+KubeOne user documentation can be found at [KubeOne docs website](https://docs.kubermatic.com/kubeone/v1.6/)
 
 ## Development Documentation
 

docs/proposals/20200224-apply.md

@@ -259,6 +259,6 @@ the specific operation.
 * Write and/or update documentation
 
 [etcd-quorum]: https://etcd.io/docs/v3.5/faq/#why-an-odd-number-of-cluster-members
-[manual-cluster-repair]: https://docs.kubermatic.com/kubeone/main/guides/manual-cluster-repair/
+[manual-cluster-repair]: https://docs.kubermatic.com/kubeone/v1.6/guides/manual-cluster-repair/
 [automated-cluster-repairs]: https://github.com/kubermatic/kubeone/pull/888
-[disaster-recovery]: https://docs.kubermatic.com/kubeone/main/guides/manual-cluster-recovery/
+[disaster-recovery]: https://docs.kubermatic.com/kubeone/v1.6/guides/manual-cluster-recovery/

docs/release_process.md

@@ -87,5 +87,5 @@ It's recommended to try to download to the release from GitHub after it's
 available and compare the checksums, as well as, confirm that `kubeone version`
 shows the correct version.
 
-[docs-compatibility]: https://docs.kubermatic.com/kubeone/main/architecture/compatibility/
+[docs-compatibility]: https://docs.kubermatic.com/kubeone/v1.6/architecture/compatibility/
 [changelog]: https://github.com/kubermatic/kubeone/blob/main/CHANGELOG.md

examples/terraform/aws-dualstack/README.md

@@ -5,11 +5,11 @@ infrastructure for a Kubernetes HA cluster with dualstack (IPv4+IPv6) support. C
 [Creating Infrastructure guide][docs-infrastructure] to learn more about how to
 use the configs and how to provision a Kubernetes cluster using KubeOne.
 
-[docs-infrastructure]: https://docs.kubermatic.com/kubeone/main/guides/using-terraform-configs/
+[docs-infrastructure]: https://docs.kubermatic.com/kubeone/v1.6/guides/using-terraform-configs/
 
 ## AWS external CCM cloud-config
 KubeOne will use following cloud-config when provisioning the cluster using external AWS CCM.
-You can [override](https://docs.kubermatic.com/kubeone/main/references/kubeone-cluster-v1beta2/#cloudproviderspec) the cloud-config
+You can [override](https://docs.kubermatic.com/kubeone/v1.6/references/kubeone-cluster-v1beta2/#cloudproviderspec) the cloud-config
 but you must specify all the options shown below. Otherwise CCM fails to initialize nodes with proper IP addresses
 and host network pods don't get dualstack IPs.