kilo
kilo copied to clipboard
squat
Kilo is a multi-cloud network overlay built on WireGuard and designed for Kubernetes (k8s + wg = kg)
This is a re-implementation of https://github.com/squat/kilo/pull/98. A rebase was not possible so the code was rewritten but without any logic changes. I deployed it in a test cluster running in...
# Why We were repeatedly expecting connectivity issues when scaling larger clusters up/down and believe it's related to the way kilo applies changes to the iptables when nodes are added/removed:...
We faced some issues with misconfigured iptables when kilo is used in conjunction with kube-router. While this PR does not fix the underlying issue, it does optionally allow enabling a...
We've been looking into making kilo rollouts not resulting in a network-related downtime that's the result of cleanup on shutdown. From what I can tell almost all operations are already...
A change in boringtun's cli caused the boringtun container to crash. Signed-off-by: leonnicolas
Currently, when running kilo in full mode (not the addon mode) only IPv4 addresses get assigned to the running pods. Could a dual stack support be added to the project...
I have an issue where when I connect an outside peer (eg. my laptop) to the cluster, `kilo` sees that configurations aren't the same and recreates the mesh to reconcile...
## Setup * one EC2 instance running Amazon Linux 2 with a public IP, Kubernetes 1.24 bootstrapped via `kubeadm init ...` * one VM on my laptop, running Fedora 35,...
Hi, I just tried kilo with k3s and flannel. It looks great. At CAST AI we are developing managed multi-cloud k8s solution. Currently we use cloud provider's VPN gateways and...
No errors on pod deployment; pods report READY and are, indeed, running when inspected directly on the node. `wg kilo0` is up and working correctly. The issue only seems to...
