-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathansible-inventory.example.ini
42 lines (30 loc) · 1.45 KB
/
ansible-inventory.example.ini
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
# this is an example ansible-inventory for NIployments,
# there are three sections: routers, controlplane and workers.
# (nodes is a parent group of controlplane and workers)
[routers]
#while unusual, you can define multiple routers.
#You MUST always have only 1 router that is master, for VRRP.
# while bootstrapping you MUST leave this group out, but you will be asked to fill it in.
#router1 ansible_ssh_host=10.0.0.1 master=true
#router2 ansible_ssh_host=10.0.0.2 master=false
[controlplane]
# These are the kind of nodes that are responsible for managing
# the Kubernetes cluster, to make a cluster High Availability,
# you should have at least 3 controlplane nodes.
# if you wish, you can specify an alias for a node, or you can just specify
# the ip address as shown below:
# you need to always define the ansible_ssh_host and ansible_ssh_private_key because they will be changed automatically
# you maybe to need to define the external interface (that will be given to the router, alongside the whole PCI device).
#node1 ansible_ssh_host=10.0.0.2 ansible_ssh_private_key=/path/to/private_key
#node1 ansible_ssh_host=10.0.0.2 ansible_ssh_private_key=/path/to/private_key external_interface=enp1f0
[workers]
# These kinds of nodes are also connected to Kubernetes cluster,
# but don't have any management services on them.
#10.0.0.5
#10.0.0.6
[nodes:children]
controlplane
workers
[all:vars]
dev_cluster=false
ansible_python_interpreter="/usr/bin/env python3"