You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the Vault operator can use a specific IP address from metallb via the spec.LoadBalancerIP field.
This is required for those of us running on-prem clusters who have many different metallb address pools, etc.
Apologies ahead of time if I'm just confused about how this works or if missed an already-existing feature. I read through the source but Go is (not yet) my strong suit.
The text was updated successfully, but these errors were encountered:
Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.
Right now the Vault operator can use a specific IP address from metallb via the spec.LoadBalancerIP field.
This is required for those of us running on-prem clusters who have many different metallb address pools, etc.
However, this field is deprecated in k8s 1.24.
kubernetes/kubernetes#107235
Perhaps something like spec.ServiceAnnotations should be available instead so that the following pattern could be used to achieve the same purpose:
Apologies ahead of time if I'm just confused about how this works or if missed an already-existing feature. I read through the source but Go is (not yet) my strong suit.
The text was updated successfully, but these errors were encountered: