juju - reports incorrect ip address for k8s tigera enterprise deployments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Internal bare metal.
juju version 3.3.1-genericli
For a charmed k8s deployment that uses tigera enterprise and dual TOR configuration with BGP the juju status reports the incorrect ip address for each node.
In dual tor bgp config the k8s ip address is on the loopback interface and sits behind two addresses on physical nics. Example - for a node we might have
tor1 <--> nic1 - 10.33.1.13
tor2 <--> nic2 - 10.33.2.13
juju status reports 10.33.1.13 as the public ip address. The addresses on nic1 and nic2 are purely for bgp and physical redundancy. There are no reachable services on these addresses.
For accuracy juju status should report the 10.33.5.13 on the loopback interface as the public ip address of the node.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Setting a preferred public address for status display is a wart that we're working out of Juju for the upcoming version 4.0.
Juju sets it based on the first set of discovered addresses from the machine, I think based on a sort that falls back to being lexicographical. Subsequent updates from on-machine discovery won't change that address if there isn't a better candidate.