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
Is it possible to configure an K8s operator with CIDR block to be uses as Load Balancer IPs. In many cases specifying ExternalIPs on Service is not possible (3rd party Helm Chart you do not have control of, or even services that gets created dynamically by other operators). Would be very helpful to have a MetalLB style of configuration, something like: data: config: | address-pools: - name: default addresses: - 192.168.1.240-192.168.1.250
The text was updated successfully, but these errors were encountered:
That kind of configuration is supported. It is in fact the main use case
for this operator. Let us know if you have issues using this operator in
the way that you described.
On Fri, Jun 24, 2022, 7:35 PM romankuzmik ***@***.***> wrote:
Is it possible to configure an K8s operator with CIDR block to be uses as
Load Balancer IPs. In many cases specifying ExternalIPs on Service is not
possible (3rd party Helm Chart you do not have control of, or even services
that gets created dynamically by other operators). Would be very helpful to
have a MetalLB style of configuration, something like:
data: config: | address-pools: - name: default addresses: -
192.168.1.240-192.168.1.250
—
Reply to this email directly, view it on GitHub
<#90>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXCV52SXCEVUCIJPZ5LVQXWWTANCNFSM5ZYQORKQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Is it possible to configure an K8s operator with CIDR block to be uses as Load Balancer IPs. In many cases specifying ExternalIPs on Service is not possible (3rd party Helm Chart you do not have control of, or even services that gets created dynamically by other operators). Would be very helpful to have a MetalLB style of configuration, something like:
data: config: | address-pools: - name: default addresses: - 192.168.1.240-192.168.1.250
The text was updated successfully, but these errors were encountered: