Go to file

Tobias Trabelsi c8986ce2ac ci/woodpecker/push/woodpecker Pipeline was successful Details Revert "Update .woodpecker.yml" This reverts commit `d4fa9bbddb`.		2024-02-02 23:41:13 +01:00
chart/metallb-ip-floater	added docs	2023-10-20 21:57:19 +02:00
cmd	init (#1 )	2023-10-15 19:50:59 +00:00
internal	fix handling if floating ip is not yet assigned	2024-02-02 23:38:04 +01:00
.gitignore	init (#1 )	2023-10-15 19:50:59 +00:00
.woodpecker.yml	Revert "Update .woodpecker.yml"	2024-02-02 23:41:13 +01:00
Dockerfile	init (#1 )	2023-10-15 19:50:59 +00:00
LICENSE	Initial commit	2023-10-07 12:03:58 +00:00
README.md	added docs	2023-10-20 21:57:19 +02:00
config.json	init (#1 )	2023-10-15 19:50:59 +00:00
go.mod	fix handling if floating ip is not yet assigned	2024-02-02 23:38:04 +01:00
go.sum	fix handling if floating ip is not yet assigned	2024-02-02 23:38:04 +01:00

README.md

metallb-ip-floater

Checks metallb speaker pods if they announce some services. If they do, assign a given floating ip on hetzner to the k8s node that announces.

Getting Started

The deployment will use helm and the chart in chart/metallb-ip-floater.
You will need a hcloud api token and the name of your floating IP. Also your k8s nodes should be labeled in hcloud.
Expose these information to the floater as described in this example:

env:
  - name: METALLB_IP_FLOATER_LABELSELECTOR
    value: "kops.k8s.io/instance-role=Node"
  - name: METALLB_IP_FLOATER_HCLOUD_TOKEN
    value: "define_it"
  - name: METALLB_IP_FLOATER_FLOATING_IP_NAME
    value: "define_it"

you can also create a secret manually with these information and reference the existing secret like this in the values.yaml:

externalConfigSecret:
  enabled: true
  name: "my-existing-secret"

Now you are able to deploy:

kubectl create namespace metallb-ip-floater
cd chart/metallb-ip-floater
helm upgrade --install -f values.yaml -n metallb-ip-floater metallb-ip-floater ./

Made with ♡ by the folkes at uploadfilter24.eu :)