border: serve only border_agent on the core node's agent

border_node is always pinned to a specific agent by the builder
(SchedulableToAgentFromAgentUUIDMixin) and its driver ships where the
data plane lives: the realm node image or the dedicated border VM image.
Advertising it from the core agent risked an unpinned border_node being
scheduled onto the core node (the scheduler takes the first capable
agent), mirroring how paas_lb_node lives only in the lbaas VM image.

Also add border_agent to the bootstrap [universal_agent_scheduler]
rewrite, which fully replaces the section and silently dropped it.

Author: gmelikov

etc/exordos_universal_agent/exordos_universal_agent.conf.j2

@@ -18,7 +18,6 @@ caps_drivers =
     CoreDNSCertificateCapabilityDriver,
     LBAgentCapabilityDriver,
     BorderAgentCapabilityDriver,
-    BorderCapabilityDriver,
     GuestMachineCapabilityDriver,
     SSHKeyCapabilityDriver,
     RenderAgentDriver
@@ -31,8 +30,7 @@ capabilities =
     certificate,
     paas_lb_agent,
     repo_proxy_installed_element,
-    border_agent,
-    border_node
+    border_agent
 
 
 [CoreDNSCertificateCapabilityDriver]

exordos_core/cmd/bootstrap.py

@@ -415,7 +415,8 @@ def _migrate_installed_elements_configs() -> None:
     password,
     certificate,
     paas_lb_agent,
-    repo_proxy_installed_element
+    repo_proxy_installed_element,
+    border_agent
 """
     try:
         with open(UA_CONFIG_PATH, "r", encoding="utf-8") as f: