kubespray/docs/getting-started.md

2.4 KiB

Getting started

The easiest way to run the deployement is to use the kubespray-cli tool. A complete documentation can be found in its github repository.

Here is a simple example on AWS:

  • Create instances and generate the inventory
kubespray aws --instances 3
  • Run the deployment
kubespray deploy --aws -u centos -n calico

Building your own inventory

Ansible inventory can be stored in 3 formats: YAML, JSON, or INI-like. There is an example inventory located here.

You can use an inventory generator to create or modify an Ansible inventory. Currently, it is limited in functionality and is only use for making a basic Kubespray cluster, but it does support creating large clusters. It now supports separated ETCD and Kubernetes master roles from node role if the size exceeds a certain threshold. Run inventory.py help for more information.

Example inventory generator usage:

cp -r inventory my_inventory
declare -a IPS=(10.10.1.3 10.10.1.4 10.10.1.5)
CONFIG_FILE=my_inventory/inventory.cfg python3 contrib/inventory_builder/inventory.py ${IPS[@]}

Starting custom deployment

Once you have an inventory, you may want to customize deployment data vars and start the deployment:

IMPORTANT: Edit my_inventory/groups_vars/*.yaml to override data vars

ansible-playbook -i my_inventory/inventory.cfg cluster.yml -b -v \
  --private-key=~/.ssh/private_key

See more details in the ansible guide.

Adding nodes

You may want to add worker nodes to your existing cluster. This can be done by re-running the cluster.yml playbook, or you can target the bare minimum needed to get kubelet installed on the worker and talking to your masters. This is especially helpful when doing something like autoscaling your clusters.

  • Add the new worker node to your inventory under kube-node (or utilize a dynamic inventory).
  • Run the ansible-playbook command, substituting scale.yml for cluster.yml:
ansible-playbook -i my_inventory/inventory.cfg scale.yml -b -v \
  --private-key=~/.ssh/private_key