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
Who is this for and what problem do they have today?
Instead of checking the cluster resource for the external IPs and node ports, a user should be given the option of creating a load-balancer for bootstrapping purposes, which would return the advertised addresses of the external listener.
> rpk cluster info --brokers x.x.x.x:9092
..
BROKERS
=======
ID HOST PORT
0* 10.128.x.x 31427
Additional notes
This is related to #3790, which adds support for specifying the preferred external address type. Those advertised addresses would be returned through the load balancer as part of the bootstrapping phase.
The text was updated successfully, but these errors were encountered:
Who is this for and what problem do they have today?
Instead of checking the cluster resource for the external IPs and node ports, a user should be given the option of creating a load-balancer for bootstrapping purposes, which would return the advertised addresses of the external listener.
What are the success criteria?
Provide an interface similar to the following:
that allows communication as follows
Additional notes
This is related to #3790, which adds support for specifying the preferred external address type. Those advertised addresses would be returned through the load balancer as part of the bootstrapping phase.
The text was updated successfully, but these errors were encountered: