You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit changes all package paths from squat/kilo to kilo-io/kilo
and the docker image name from squat/kilo to kiloio/squat.
The API name and comments regarding the website kilo.squat.ai are
unchanged.
Signed-off-by: leonnicolas <leonloechner@gmx.de>
Copy file name to clipboardExpand all lines: docs/kgctl.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -6,20 +6,20 @@ This tool can be used to understand a mesh's topology, get the WireGuard configu
6
6
7
7
## Installation
8
8
9
-
The `kgctl` binary is automatically compiled for Linux, macOS, and Windows for every release of Kilo and can be downloaded from [the GitHub releases page](https://github.com/squat/kilo/releases/latest).
9
+
The `kgctl` binary is automatically compiled for Linux, macOS, and Windows for every release of Kilo and can be downloaded from [the GitHub releases page](https://github.com/kilo-io/kilo/releases/latest).
10
10
11
11
### Building from Source
12
12
Kilo is written in Golang and as a result the [Go toolchain must be installed](https://golang.org/doc/install) in order to build the `kgctl` binary.
13
13
To download the Kilo source code and then build and install `kgctl` using the latest commit all with a single command, run:
14
14
15
15
```shell
16
-
go install github.com/squat/kilo/cmd/kgctl@latest
16
+
go install github.com/kilo-io/kilo/cmd/kgctl@latest
17
17
```
18
18
19
19
Alternatively, `kgctl` can be built and installed based on specific version of the code by specifying a Git tag or hash, e.g.:
20
20
21
21
```shell
22
-
go install github.com/squat/kilo/cmd/kgctl@0.2.0
22
+
go install github.com/kilo-io/kilo/cmd/kgctl@0.2.0
23
23
```
24
24
25
25
When working on Kilo locally, it can be helpful to build and test the `kgctl` binary as part of the development cycle.
> **Note**: even if some nodes have the WireGuard kernel module, this configuration will cause all nodes to use the userspace implementation of WireGuard.
@@ -30,8 +30,8 @@ In a heterogeneous cluster where some nodes are missing the WireGuard kernel mod
30
30
An example of such a configuration for a K3s cluster can by applied with:
This configuration will deploy [nkml](https://github.com/leonnicolas/nkml) as a DaemonSet to label all nodes according to the presence of the WireGuard kernel module.
0 commit comments