Commit 7abd788d authored by Konstantinos Togias's avatar Konstantinos Togias
Browse files

docs: explain how SRM uses backend connection settings

parent c84496fc

README.md

+4 −2
Changes for README.md: 4 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -38,8 +38,10 @@ This README describes the **Release 2.0.0 implementation**, distributed as 


1. At startup, SRM uses the TF-SDK's `BootstrapTopology` discovery adapter to

   read the operator's bootstrap file. The adapter returns normalized zones,

   domains, capabilities and control-path bindings. It exposes runtime connection

   configuration through a separate accessor for SRM's control-path registry.

   domains, capabilities and control-path bindings. TF-SDK also returns each

   control path's connection settings separately from the topology data.

   SRM uses these settings, such as the backend URL or Kubernetes context and

   namespace, to configure the corresponding adapter.

2. SRM builds one adapter instance per control path with

   `build_adapter(adapter_type, config)`. Construction and capability discovery

   perform no backend I/O.