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
{{ message }}
This repository has been archived by the owner on Aug 25, 2021. It is now read-only.
When starting agent instances, the agents use the hostnames of the pods consul-{random} to register as nodes. IMHO this isn't desired and creates confusion for the operator of the consul cluster, b/c it's impossible to tell which node represents which physical k8s node.
The text was updated successfully, but these errors were encountered:
We're going to take a look soon. I just want to verify that this doesn't cause any issues with the server agents since they run alongside the client agents in K8S (due to daemonsets not respecting affinities). I don't think so since I think they set their node name to something else, but just want to be sure!
When starting agent instances, the agents use the hostnames of the pods consul-{random} to register as nodes. IMHO this isn't desired and creates confusion for the operator of the consul cluster, b/c it's impossible to tell which node represents which physical k8s node.
The text was updated successfully, but these errors were encountered: