-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
feat(k3s): Add option to set MetalLB interfaces #583
base: master
Are you sure you want to change the base?
Conversation
@@ -30,3 +30,4 @@ metal_lb_mode: layer2 | |||
metal_lb_available_timeout: 240s | |||
metal_lb_controller_tag_version: v0.14.3 | |||
metal_lb_ip_range: 192.168.30.80-192.168.30.90 | |||
metal_lb_interfaces: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be an empty list by default?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This way I can have a condition on this in metallb.crs.j2. If empty, no interfaces are set in the L2Advertisement resource, which in turn triggers the default of metallb: https://metallb.universe.tf/configuration/_advanced_l2_configuration/#specify-network-interfaces-that-lb-ip-can-be-announced-from
Let me know if there's a better default and I'll adjust.
Also add a description of the new parameter in roles/k3s_server_post/meta/main.yml. |
@kuboschek hey! Just wanted to check in to see if you could possibly make a few adjustments |
Happy to make some adjustments. I’ll schedule time for this on the weekend. |
Proposed Changes
Checklist
site.yml
playbookreset.yml
playbook