
Instead of static, local configuration (see Service Configuration), this service can run in managed mode, loading its instance configuration from the OpenID Federation Registry — a service that lets you manage trust anchors, entities, policies and trust marks through a web interface instead of editing configuration files.
When this service is running in managed mode it loads its instance configuration from a given registry.
Loading of managed configuration happens after startup, which means application will not be ready for traffic immediately. The application offers a ready state endpoint to help orchestration tools know when the service is ready for traffic.
To load modules from the registry the service needs to have an instance-id configured. This informs the service about what instance group it belongs to. Multiple instance that should be configured in the same way and loadbalanced should share the same instance id.
E.g. Pseudo Configuration of 4 nodes that is divided into two instance groups
graph LR
subgraph Instance-987
subgraph node-3
123-tmi-1("/tmi");
end
subgraph node-4
123-tmi-2("/tmi");
end
end
subgraph Instance-123
subgraph node-1
123-ta-1("/ta");
end
subgraph node-2
123-ta-2("/ta");
end
end
loadbalancer("Loadbalancer /ta | /tmi") --> 123-ta-1 & 123-ta-2;
loadbalancer --> 123-tmi-1 & 123-tmi-2;
See 2.4 Registry Integration for the
federation.registry.integration.* properties that enable managed mode and configure the
instance-id, and Management, Health and Observability
for the readiness endpoint orchestration tools should poll.