Select Git revision
-
Michael Shnit authored
* Add AWS ALB Ingress Controller Ansible role * remove trailing spaces * update owners * ALB ingress: update rbac clusterrole and remove role * Move alb-ingress role to roles/kubernetes-apps/ingress_controller folder
Michael Shnit authored* Add AWS ALB Ingress Controller Ansible role * remove trailing spaces * update owners * ALB ingress: update rbac clusterrole and remove role * Move alb-ingress role to roles/kubernetes-apps/ingress_controller folder
ansible.md 7.59 KiB
Ansible variables
Inventory
The inventory is composed of 3 groups:
- kube-node : list of kubernetes nodes where the pods will run.
- kube-master : list of servers where kubernetes master components (apiserver, scheduler, controller) will run.
- etcd: list of servers to compose the etcd server. You should have at least 3 servers for failover purpose.
Note: do not modify the children of k8s-cluster, like putting the etcd group into the k8s-cluster, unless you are certain to do that and you have it fully contained in the latter:
k8s-cluster ⊂ etcd => kube-node ∩ etcd = etcdWhen kube-node contains etcd, you define your etcd cluster to be as well schedulable for Kubernetes workloads. If you want it a standalone, make sure those groups do not intersect. If you want the server to act both as master and node, the server must be defined on both groups kube-master and kube-node. If you want a standalone and unschedulable master, the server must be defined only in the kube-master and not kube-node.
There are also two special groups:
- calico-rr : explained for advanced Calico networking cases
- bastion : configure a bastion host if your nodes are not directly reachable
Below is a complete inventory example: