mysql-router on a host with a VIP may incorrectly use the VIP to communicate with the cluster

Occasionally, mysqlrouter will fail to communicate with the mysql-innodb-cluster with the following error:

Note in the following example:

Space IP: 10.5.0.28
VIP: 10.5.254.100

Failed to bootstrap mysqlrouter: Error: Unable to connect to the metadata server: Error connecting to MySQL server at 10.5.0.24:0: Access denied for user 'mysqlrouteruser'@'10.5.254.100' (using password: YES) (1045)

This even after confirmation that the db-router relationship is fulfilled and the mysql-innodb-cluster has proper grants for the unit's Space IP.

ip addr
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8958 qdisc fq_codel state UP group default qlen 1000
    link/ether fa:16:3e:b5:19:26 brd ff:ff:ff:ff:ff:ff
    inet 10.5.254.100/16 brd 10.5.255.255 scope global ens3
       valid_lft forever preferred_lft forever
    inet 10.5.0.28/16 brd 10.5.255.255 scope global secondary dynamic ens3
       valid_lft 62597sec preferred_lft 62597sec
    inet6 fe80::f816:3eff:feb5:1926/64 scope link
       valid_lft forever preferred_lft forever

If the VIP becomes the "default" address the unit uses to communicate, communication is broken as the mysql-innodb-cluster unit has not granted the VIP address any permissions.