Force use one api-endpoint on controllers

juju
1

Hi guys, I’m facing the situation where I have juju controller bootstraped in a machine with several interfaces, despite I have setup one interface on add-cloud creations is adding additional interfaces who belongs to Docker or virtual machines, is there any extra command on bootstrap stage to force use only one interface?
FYI those extra interfaces were added while adding a new model.

what I have after bootstrap :

uuid: bb4621ae-cd40-487e-838d-9427355025a5
controller-uuid: bb4621ae-cd40-487e-838d-9427355025a5
api-endpoints: [ ‘10.0.100.100:17070’]
cloud: idtolu-cloud

and after run add model:

uuid: bb4621ae-cd40-487e-838d-9427355025a5
controller-uuid: bb4621ae-cd40-487e-838d-9427355025a5
api-endpoints: [‘172.24.0.1:17070’, ‘10.0.100.100:17070’, ‘172.17.0.1:17070’,
‘172.25.0.1:17070’, ‘172.26.0.1:17070’, ‘172.27.0.1:17070’]
cloud: idtolu-cloud

any help appreciated

2

If you create a space with the subnet you want to communicate with the controller on, you can set the controller config for juju-mgmt-space to that space.

This will then limit what agents use to communicate with controllers. More info here: https://discourse.charmhub.io/t/configuring-controllers/1107

The client gets updated with all addresses, but when you connect, the one you used (known good) goes to the front of the list as the preferred one to use. If you edit it to be like that and can always access the controller there, you should always be hitting on that address.