c12s-kubespray/roles/network_plugin/flannel/defaults/main.yml

---
# Flannel public IP
# The address that flannel should advertise as how to access the system
flannel_public_ip: "{{ access_ip|default(ip|default(ansible_default_ipv4.address)) }}"

## interface that should be used for flannel operations
## This is actually an inventory node-level item
# flannel_interface:

# You can choose what type of flannel backend to use
# please refer to flannel's docs : https://github.com/coreos/flannel/blob/master/README.md
flannel_backend_type: "vxlan"

# Limits for apps
flannel_memory_limit: 500M
flannel_cpu_limit: 300m
flannel_memory_requests: 256M
flannel_cpu_requests: 150m

flannel_cert_dir: /etc/flannel/certs
etcd_cert_dir: /etc/ssl/etcd/ssl
Add flannel vars to enable vagrant and amazon environments 2016-01-23 18:27:06 +00:00			`---`
Add variables and defaults for multiple types of ip addresses. Each node can have 3 IPs. 1. ansible_default_ip4 - whatever ansible things is the first IPv4 address usually with the default gw. 2. ip - An address to use on the local node to bind listeners and do local communication. For example, Vagrant boxes have a first address that is the NAT bridge and is common for all nodes. The second address/interface should be used. 3. access_ip - An address to use for node-to-node access. This is assumed to be used by other nodes to access the node and may not be actually assigned on the node. For example, AWS public ip that is not assigned to node. This updates the places addresses are used to use either ip or access_ip and walk up the list to find an address. 2016-01-26 20:41:42 +00:00			`# Flannel public IP`
			`# The address that flannel should advertise as how to access the system`
			`flannel_public_ip: "{{ access_ip\|default(ip\|default(ansible_default_ipv4.address)) }}"`
Add flannel vars to enable vagrant and amazon environments 2016-01-23 18:27:06 +00:00
			`## interface that should be used for flannel operations`
Add variables and defaults for multiple types of ip addresses. Each node can have 3 IPs. 1. ansible_default_ip4 - whatever ansible things is the first IPv4 address usually with the default gw. 2. ip - An address to use on the local node to bind listeners and do local communication. For example, Vagrant boxes have a first address that is the NAT bridge and is common for all nodes. The second address/interface should be used. 3. access_ip - An address to use for node-to-node access. This is assumed to be used by other nodes to access the node and may not be actually assigned on the node. For example, AWS public ip that is not assigned to node. This updates the places addresses are used to use either ip or access_ip and walk up the list to find an address. 2016-01-26 20:41:42 +00:00			`## This is actually an inventory node-level item`
Add flannel vars to enable vagrant and amazon environments 2016-01-23 18:27:06 +00:00			`# flannel_interface:`
flannel backend type option 2016-03-04 10:25:01 +00:00
			`# You can choose what type of flannel backend to use`
			`# please refer to flannel's docs : https://github.com/coreos/flannel/blob/master/README.md`
			`flannel_backend_type: "vxlan"`
Systemd units, limits, and bin path fixes * Add restart for weave service unit * Reuse docker_bin_dir everythere * Limit systemd managed docker containers by CPU/RAM. Do not configure native systemd limits due to the lack of consensus in the kernel community requires out-of-tree kernel patches. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com> 2016-12-23 14:44:44 +00:00
			`# Limits for apps`
			`flannel_memory_limit: 500M`
			`flannel_cpu_limit: 300m`
			`flannel_memory_requests: 256M`
			`flannel_cpu_requests: 150m`
Fix cert paths for flannel/calico policy apps Signed-off-by: Bogdan Dobrelya <bogdando@mail.ru> 2016-12-30 12:47:12 +00:00
			`flannel_cert_dir: /etc/flannel/certs`
			`etcd_cert_dir: /etc/ssl/etcd/ssl`