Lucas Servén Marín 5277ab5bad

docs,pkg: use new well-known region label

This commit updates the well-known label to determine the region of the
node to topology.kubernetes.io/region, which is the new standard as
defined by the Kubernetes documentation, now that
failure-domain.beta.kubernetes.io/region has been deprecated.

2020-01-07 18:41:55 +01:00

3.8 KiB

Raw Blame History

Annotations

The following annotations can be added to any Kubernetes Node object to configure the Kilo network.

Name	type	example
kilo.squat.ai/force-external-ip	CIDR	`"55.55.55.55/32"`
kilo.squat.ai/force-internal-ip	CIDR	`"55.55.55.55/32"`
kilo.squat.ai/leader	string	`""`
kilo.squat.ai/location	string	`"gcp-east"`

force-external-ip

Kilo requires at least one node in each location to have a publicly accessible IP address in order to create links to other locations. The Kilo agent running on each node will use heuristics to automatically detect an external IP address for the node; however, in some circumstances it may be necessary to explicitly configure the IP address, for example:

no automatic public IP on ethernet device: on some cloud providers it is common for nodes to be allocated a public IP address but for the Ethernet devices to only be automatically configured with the private network address; in this case the allocated public IP address should be specified;
multiple public IP addresses: if a node has multiple public IPs but one is preferred, then the preferred IP address should be specified;
IPv6: if a node has both public IPv4 and IPv6 addresses and the Kilo network should operate over IPv6, then the IPv6 address should be specified.

force-internal-ip

Kilo routes packets destined for nodes inside the same logical location using the node's internal IP address. The Kilo agent running on each node will use heuristics to automatically detect a private IP address for the node; however, in some circumstances it may be necessary to explicitly configure the IP address, for example:

multiple private IP addresses: if a node has multiple private IPs but one is preferred, then the preferred IP address should be specified;
IPv6: if a node has both private IPv4 and IPv6 addresses and the Kilo network should operate over IPv6, then the IPv6 address should be specified.

leader

By default, Kilo creates a network mesh at the data-center granularity. This means that one leader node is selected from each location to be an edge server and act as the gateway to other locations; the network topology will be a full mesh between leaders. Kilo automatically selects the leader for each location in a stable and deterministic manner to avoid churn in the network configuration, while giving preference to nodes that are known to have public IP addresses. In some situations it may be desirable to manually select the leader for a location, for example:

firewall: Kilo requires an open UDP port, which defaults to 51820, to communicate between locations; if only one node is configured to have that port open, then that node should be given the leader annotation;
bandwidth: if certain nodes in the cluster have a higher bandwidth or lower latency Internet connection, then those nodes should be given the leader annotation.

Note: multiple nodes within a single location can be given the leader annotation; in this case, Kilo will select one leader from the set of annotated nodes.

location

Kilo allows nodes in different logical or physical locations to route packets to one-another. In order to know what connections to create, Kilo needs to know which nodes are in each location. Kilo will try to infer each node's location from the topology.kubernetes.io/region node label. If the label is not present for a node, for example if running a bare-metal cluster or on an unsupported cloud provider, then the location annotation should be specified.

Note: all nodes without a defined location will be considered to be in the default location "".

3.8 KiB Raw Blame History