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
When trying to figure out how to influence which IP address gets included in the generated kubeconfig file, I realized that the charm action is using "unit-get public-address". Since unit-get is deprecated, should this be modified to use network-get? Either on the cluster interface or a newly defined interface, maybe public?
The text was updated successfully, but these errors were encountered:
The blocking issue here is that "unit-get public-address" returns the public ingress address which isn't always available from any of the network-get commands. Some discussion about that can be seen here: https://bugs.launchpad.net/juju/+bug/1924780/comments/13
When trying to figure out how to influence which IP address gets included in the generated kubeconfig file, I realized that the charm action is using "unit-get public-address". Since unit-get is deprecated, should this be modified to use network-get? Either on the cluster interface or a newly defined interface, maybe public?
The text was updated successfully, but these errors were encountered: