kubernetes-sigs
/
kubespray
mirror of https://github.com/kubernetes-sigs/kubespray.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
kubespray/roles/network_plugin/flannel/defaults/main.yml

29 lines
1.0 KiB
YAML
Raw Normal View History

Add flannel vars to enable vagrant and amazon environments
2016-01-24 02:27:06 +08: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-27 04:41:42 +08:00
# Flannel public IP
# The address that flannel should advertise as how to access the system
Initial version of Flannel using CNI (#1486) * Updates Controller Manager/Kubelet with Flannel's required configuration for CNI * Removes old Flannel installation * Install CNI enabled Flannel DaemonSet/ConfigMap/CNI bins and config (with portmap plugin) on host * Uses RBAC if enabled * Fixed an issue that could occur if br_netfilter is not a module and net.bridge.bridge-nf-call-iptables sysctl was not set
2017-08-25 15:07:50 +08:00
# Disabled until https://github.com/coreos/flannel/issues/712 is fixed
Remove serialized collect of ansible_default_ipv4 The fallback_ips tasks are essentially serializing the gathering of one fact on all the hosts, which can have dramatic performance implications on large clusters (several minutes). This is essentially a reversal of 35f248dff0ddb430e2293af98ba73aa5062c89c1 Being able to run without refreshing the cache facts is not worth it. We keep fallback_ip for now, simply changing the access to a normal hostvars variable instead of a custom dictionnary.
2024-09-30 20:24:51 +08:00
# flannel_public_ip: "{{ access_ip | default(ip | default(fallback_ip)) }}"
Add flannel vars to enable vagrant and amazon environments
2016-01-24 02:27:06 +08:00
## interface that should be used for flannel operations
Add --iface-regex options to flannel Flannel use interface for inter-host communication setted on --iface options Defaults to the interface for the default route on the machine. flannel config set via daemonset, and flannel config on all nodes is the same. But different nodes can have different interface names for the inter-host communication network The option --iface-regex allows the flannel to find the interface on which the address is set from the inter-host communication network
2018-03-17 02:44:36 +08:00
## This is actually an inventory cluster-level item
Add flannel vars to enable vagrant and amazon environments
2016-01-24 02:27:06 +08:00
# flannel_interface:
flannel backend type option
2016-03-04 18:25:01 +08:00
Add --iface-regex options to flannel Flannel use interface for inter-host communication setted on --iface options Defaults to the interface for the default route on the machine. flannel config set via daemonset, and flannel config on all nodes is the same. But different nodes can have different interface names for the inter-host communication network The option --iface-regex allows the flannel to find the interface on which the address is set from the inter-host communication network
2018-03-17 02:44:36 +08:00
## Select interface that should be used for flannel operations by regexp on Name or IP
## This is actually an inventory cluster-level item
## example: select interface with ip from net 10.0.0.0/23
## single quote and escape backslashes
# flannel_interface_regexp: '10\\.0\\.[0-2]\\.\\d{1,3}'
flannel backend type option
2016-03-04 18:25:01 +08: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"
Allow configureable vni and port for flannel overlay (#5939)
2020-04-15 18:14:02 +08:00
flannel_vxlan_vni: 1
flannel_vxlan_port: 8472
Add variable to set direct routing on flannel VXLAN (#9438)
2022-11-01 04:16:45 +08:00
flannel_vxlan_direct_routing: false
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 22:44:44 +08:00
# Limits for apps
flannel_memory_limit: 500M
flannel_cpu_limit: 300m
Lower default memory requests This is to address out of memory issues on CI as well as help fit deployments for people starting out with kargo on smaller machines
2017-02-28 00:53:43 +08:00
flannel_memory_requests: 64M
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 22:44:44 +08:00
flannel_cpu_requests: 150m