anton-vinogradov opened a new pull request, #13851: URL: https://github.com/apache/ignite/pull/13851
[IGNITE-29305](https://issues.apache.org/jira/browse/IGNITE-29305) moves the SSL factory registry to the common component lifecycle. `IgniteKernal` no longer starts and stops it with direct calls. ## Changes - `SslFactoryRegistry` is a processor. It starts hot reload in `onKernalStart` and stops it in `onKernalStop`. All four transports register their factories during `start()`, so they are registered by then. - The node starts the registry right after the client connector and REST processors. They stop their servers in their own `onKernalStop`, and the node calls `onKernalStop` in reverse start order, so hot reload stops before them. Discovery and communication stop later, in the managers' `stop()`. - `GridKernalContextImpl` still creates the registry, so `ctx.ssl()` stays available in test contexts that start SPIs without `IgniteKernal`. It creates the registry in its constructor after the configuration is set, because a processor takes its logger from the configuration. - For the same reason, `GridTestKernalContext` sets the logger in the configuration before the context constructor runs. ## Tests - A node test checks that the registry follows the client connector and REST processors among the node components. - The registry tests drive the registry through `onKernalStart` and `onKernalStop`. - The existing hot reload tests on live nodes and the `control.sh --ssl reload` tests pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
