Bastion host approach and Existing Wireguard Network #399
Description
Hello Dear Community.
I like the idea and freedom behind kilo, but i am struggling to apply it for my setup.
I have central server which just has wireguard easy and exposes existing wireguard endpoint.
Then I have 3 k3s clusters in different cities, one of them even doesnt have public IP. They have wireguard clients which successfully connected to bastion server, and entire network works pretty perfect.
I would like to add kilo to each cluster - to connect them into network via existing wireguard endpoint on bastion host. It will be like snowflake.
Then, i would like all pods inside those connected clusters easily communicate between geographies, for better failover - so i can reconnect services to other backends, etc.
But i even struggling to install kilo agents. Applying manifests little bit confusing. As - i cannot see where to configure endpoints. I beleve everything is already setup for autodiscovery, but not for my case.