You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/setup/production-environment/tools/kubespray.md
+27-26Lines changed: 27 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,22 +6,22 @@ weight: 30
6
6
7
7
{{% capture overview %}}
8
8
9
-
This quickstart helps to install a Kubernetes cluster hosted on GCE, Azure, OpenStack, AWS, vSphere, Oracle Cloud Infrastructure (Experimental) or Baremetal with [Kubespray](https://github.com/kubernetes-incubator/kubespray).
9
+
This quickstart helps to install a Kubernetes cluster hosted on GCE, Azure, OpenStack, AWS, vSphere, Packet (bare metal), Oracle Cloud Infrastructure (Experimental) or Baremetal with [Kubespray](https://github.com/kubernetes-sigs/kubespray).
10
10
11
-
Kubespray is a composition of [Ansible](http://docs.ansible.com/) playbooks, [inventory](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/ansible.md), provisioning tools, and domain knowledge for generic OS/Kubernetes clusters configuration management tasks. Kubespray provides:
11
+
Kubespray is a composition of [Ansible](http://docs.ansible.com/) playbooks, [inventory](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/ansible.md), provisioning tools, and domain knowledge for generic OS/Kubernetes clusters configuration management tasks. Kubespray provides:
12
12
13
13
* a highly available cluster
14
14
* composable attributes
15
15
* support for most popular Linux distributions
16
16
* Container Linux by CoreOS
17
-
* Debian Jessie, Stretch, Wheezy
17
+
* Debian Buster, Jessie, Stretch, Wheezy
18
18
* Ubuntu 16.04, 18.04
19
-
* CentOS/RHEL 7
20
-
* Fedora/CentOS Atomic
21
-
* openSUSE Leap 42.3/Tumbleweed
19
+
* CentOS/RHEL/Oracle Linux 7
20
+
* Fedora 28
21
+
* openSUSE Leap 15
22
22
* continuous integration tests
23
23
24
-
To choose a tool which best fits your use case, read [this comparison](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/comparisons.md) to [kubeadm](/docs/admin/kubeadm/) and [kops](../kops).
24
+
To choose a tool which best fits your use case, read [this comparison](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/comparisons.md) to [kubeadm](/docs/admin/kubeadm/) and [kops](../kops).
25
25
26
26
{{% /capture %}}
27
27
@@ -31,11 +31,11 @@ To choose a tool which best fits your use case, read [this comparison](https://g
31
31
32
32
### (1/5) Meet the underlay requirements
33
33
34
-
Provision servers with the following [requirements](https://github.com/kubernetes-incubator/kubespray#requirements):
34
+
Provision servers with the following [requirements](https://github.com/kubernetes-sigs/kubespray#requirements):
35
35
36
-
***Ansible v2.5 (or newer) and python-netaddr is installed on the machine that will run Ansible commands**
36
+
***Ansible v2.7.8 and python-netaddr is installed on the machine that will run Ansible commands**
37
37
***Jinja 2.9 (or newer) is required to run the Ansible Playbooks**
38
-
* The target servers must have **access to the Internet** in order to pull docker images
38
+
* The target servers must have access to the Internet in order to pull docker images. Otherwise, additional configuration is required ([See Offline Environment](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/downloads.md#offline-environment))
39
39
* The target servers are configured to allow **IPv4 forwarding**
40
40
***Your ssh key must be copied** to all the servers part of your inventory
41
41
* The **firewalls are not managed**, you'll need to implement your own rules the way you used to. in order to avoid any issue during deployment you should disable your firewall
@@ -44,12 +44,13 @@ Provision servers with the following [requirements](https://github.com/kubernete
44
44
Kubespray provides the following utilities to help provision your environment:
45
45
46
46
*[Terraform](https://www.terraform.io/) scripts for the following cloud providers:
After you provision your servers, create an [inventory file for Ansible](http://docs.ansible.com/ansible/intro_inventory.html). You can do this manually or via a dynamic inventory script. For more information, see "[Building your own inventory](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md#building-your-own-inventory)".
53
+
After you provision your servers, create an [inventory file for Ansible](http://docs.ansible.com/ansible/intro_inventory.html). You can do this manually or via a dynamic inventory script. For more information, see "[Building your own inventory](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/getting-started.md#building-your-own-inventory)".
53
54
54
55
### (3/5) Plan your cluster deployment
55
56
@@ -58,64 +59,64 @@ Kubespray provides the ability to customize many aspects of the deployment:
58
59
* Choice deployment mode: kubeadm or non-kubeadm
59
60
* CNI (networking) plugins
60
61
* DNS configuration
61
-
* Choice of control plane: native/binary or containerized with docker or rkt
62
+
* Choice of control plane: native/binary or containerized
62
63
* Component versions
63
64
* Calico route reflectors
64
65
* Component runtime options
65
66
* {{< glossary_tooltip term_id="docker" >}}
66
-
* {{< glossary_tooltip term_id="rkt" >}}
67
+
* {{< glossary_tooltip term_id="containerd" >}}
67
68
* {{< glossary_tooltip term_id="cri-o" >}}
68
-
* Certificate generation methods (**Vault being discontinued**)
69
+
* Certificate generation methods
69
70
70
71
Kubespray customizations can be made to a [variable file](http://docs.ansible.com/ansible/playbooks_variables.html). If you are just getting started with Kubespray, consider using the Kubespray defaults to deploy your cluster and explore Kubernetes.
71
72
72
73
### (4/5) Deploy a Cluster
73
74
74
75
Next, deploy your cluster:
75
76
76
-
Cluster deployment using [ansible-playbook](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md#starting-custom-deployment).
77
+
Cluster deployment using [ansible-playbook](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/getting-started.md#starting-custom-deployment).
Large deployments (100+ nodes) may require [specific adjustments](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/large-deployments.md) for best results.
84
+
Large deployments (100+ nodes) may require [specific adjustments](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/large-deployments.md) for best results.
84
85
85
86
### (5/5) Verify the deployment
86
87
87
-
Kubespray provides a way to verify inter-pod connectivity and DNS resolve with [Netchecker](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/netcheck.md). Netchecker ensures the netchecker-agents pods can resolve DNS requests and ping each over within the default namespace. Those pods mimic similar behavior of the rest of the workloads and serve as cluster health indicators.
88
+
Kubespray provides a way to verify inter-pod connectivity and DNS resolve with [Netchecker](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/netcheck.md). Netchecker ensures the netchecker-agents pods can resolve DNS requests and ping each over within the default namespace. Those pods mimic similar behavior of the rest of the workloads and serve as cluster health indicators.
88
89
89
90
## Cluster operations
90
91
91
92
Kubespray provides additional playbooks to manage your cluster: _scale_ and _upgrade_.
92
93
93
94
### Scale your cluster
94
95
95
-
You can add worker nodes from your cluster by running the scale playbook. For more information, see "[Adding nodes](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md#adding-nodes)".
96
-
You can remove worker nodes from your cluster by running the remove-node playbook. For more information, see "[Remove nodes](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md#remove-nodes)".
96
+
You can add worker nodes from your cluster by running the scale playbook. For more information, see "[Adding nodes](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/getting-started.md#adding-nodes)".
97
+
You can remove worker nodes from your cluster by running the remove-node playbook. For more information, see "[Remove nodes](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/getting-started.md#remove-nodes)".
97
98
98
99
### Upgrade your cluster
99
100
100
-
You can upgrade your cluster by running the upgrade-cluster playbook. For more information, see "[Upgrades](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/upgrades.md)".
101
+
You can upgrade your cluster by running the upgrade-cluster playbook. For more information, see "[Upgrades](https://github.com/kubernetes-sigs/kubespray/blob/master/docs/upgrades.md)".
101
102
102
103
## Cleanup
103
104
104
-
You can reset your nodes and wipe out all components installed with Kubespray via the [reset playbook](https://github.com/kubernetes-incubator/kubespray/blob/master/reset.yml).
105
+
You can reset your nodes and wipe out all components installed with Kubespray via the [reset playbook](https://github.com/kubernetes-sigs/kubespray/blob/master/reset.yml).
105
106
106
107
{{< caution >}}
107
108
When running the reset playbook, be sure not to accidentally target your production cluster!
0 commit comments