Commits on Feb 1, 2019

1. Register all kubernetes services to the k8s-sync node …

   Registering the services with their node information causes issues with
   anti-entropy on the clients because they are registered directly with
   the servers rather than the clients. So, the clients don't have a record
   of the service and deregister them. This causes a register/deregister loop
   because the sync process automatically re-registers them.
   
   Given that the sync doesn't register things directly to the clients, it
   is more correct to register them to a synthetic node (`k8s-sync` in this
   case) to indicate that they don't follow the usual path.

   

   adilyse committed Feb 1, 2019
   Configuration menu

   • View commit details
   • Copy full SHA for ca2f384
   • Browse repository at this point

   Copy the full SHA

   ca2f384 View commit details

   Browse the repository at this point in the history