adelorenzo/kilo
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

cmd/kg,pkg: add --resync-period flag

Browse Source 
This commit introduces a new `--resync-period` flag to control how often
the Kilo controllers should reconcile.

Signed-off-by: Lucas Servén Marín <lserven@gmail.com>
This commit is contained in:
Lucas Servén Marín
2021-02-28 18:33:01 +01:00
parent c060bf24e2
commit 8dbbc636b5
8 changed files with 58 additions and 68 deletions
Download Patch File Download Diff File Expand all files Collapse all files

57
docs/kg.md
View File

@@ -16,40 +16,25 @@ The behavior of `kg` can be configured using the command line flags listed below
[embedmd]:# (../tmp/help.txt)
```txt
Usage of bin/amd64/kg:
-backend string
The backend for the mesh. Possible values: kubernetes (default "kubernetes")
-clean-up-interface
Should Kilo delete its interface when it shuts down?
-cni
Should Kilo manage the node's CNI configuration? (default true)
-cni-path string
Path to CNI config. (default "/etc/cni/net.d/10-kilo.conflist")
-compatibility string
Should Kilo run in compatibility mode? Possible values: flannel
-create-interface
Should kilo create an interface on startup? (default true)
-encapsulate string
When should Kilo encapsulate packets within a location? Possible values: never, crosssubnet, always (default "always")
-hostname string
Hostname of the node on which this process is running.
-interface string
Name of the Kilo interface to use; if it does not exist, it will be created. (default "kilo0")
-kubeconfig string
Path to kubeconfig.
-listen string
The address at which to listen for health and metrics. (default ":1107")
-local
Should Kilo manage routes within a location? (default true)
-log-level string
Log level to use. Possible values: all, debug, info, warn, error, none (default "info")
-master string
The address of the Kubernetes API server (overrides any value in kubeconfig).
-mesh-granularity string
The granularity of the network mesh to create. Possible values: location, full (default "location")
-port uint
The port over which WireGuard peers should communicate. (default 51820)
-subnet string
CIDR from which to allocate addresses for WireGuard interfaces. (default "10.4.0.0/16")
-version
Usage of bin//linux/amd64/kg:
--backend string The backend for the mesh. Possible values: kubernetes (default "kubernetes")
--clean-up-interface Should Kilo delete its interface when it shuts down?
--cni Should Kilo manage the node's CNI configuration? (default true)
--cni-path string Path to CNI config. (default "/etc/cni/net.d/10-kilo.conflist")
--compatibility string Should Kilo run in compatibility mode? Possible values: flannel
--create-interface Should kilo create an interface on startup? (default true)
--encapsulate string When should Kilo encapsulate packets within a location? Possible values: never, crosssubnet, always (default "always")
--hostname string Hostname of the node on which this process is running.
--interface string Name of the Kilo interface to use; if it does not exist, it will be created. (default "kilo0")
--kubeconfig string Path to kubeconfig.
--listen string The address at which to listen for health and metrics. (default ":1107")
--local Should Kilo manage routes within a location? (default true)
--log-level string Log level to use. Possible values: all, debug, info, warn, error, none (default "info")
--master string The address of the Kubernetes API server (overrides any value in kubeconfig).
--mesh-granularity string The granularity of the network mesh to create. Possible values: location, full (default "location")
--port uint The port over which WireGuard peers should communicate. (default 51820)
--resync-period duration How often should the Kilo controllers reconcile? (default 30s)
--subnet string CIDR from which to allocate addresses for WireGuard interfaces. (default "10.4.0.0/16")
--topology-label string Kubernetes node label used to group nodes into logical locations. (default "topology.kubernetes.io/region")
--version Print version and exit
```