-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to set wireguard IP via node annotation #221
Comments
This is mostly useful for clsters using kilo as CNI |
Kilo uses annotations on the node objects to override and force values that would otherwise be autonomously determined. Let's align this proposal with that practice, e.g. |
In cases where one needs prior knowledge of the nodes IP to for example;
A node label that can be set on cluster creation could be implemented to achieve this.
Suggesting to use a label as for most k8s distros, this can be set on node/cluster creation.
This label should indicate a
preferred
wireguard IP to be set by kilo and ignored if another node already exists with the IP.This means all other functionality can stay the same.
So in short,
kilo.squat.ai/wireguard-ip:"<IPV4 value>"
@squat
The text was updated successfully, but these errors were encountered: