v2.3.1

Patch release: services started with chapkit mlproject run register themselves with chap-core, and the run command gets options for it. This fixes the known issue listed in 2.3.0.

Fixed

• chapkit mlproject run registers with the orchestrator (chap-core) on startup when SERVICEKIT_ORCHESTRATOR_URL is set (CLIM-1340, #136). Previously it never enabled registration, so a model started this way next to chap-core in compose was never discovered, although the runner guide said it would be.
• The registered address uses the port the service listens on. Without SERVICEKIT_PORT, servicekit would have advertised 8000, so --port 9090 registered an address nothing listened on. The --port is also what is probed for readiness before registering.

Added

• chapkit mlproject run --register-url, --advertise-host and --advertise-port. Each falls back to SERVICEKIT_ORCHESTRATOR_URL, SERVICEKIT_HOST and SERVICEKIT_PORT, so compose setups work unchanged. The shared secret is only read from SERVICEKIT_REGISTRATION_KEY, so it never appears in the process list or shell history.
• The startup output shows registers with: <url> when registration is on.

Changed

• chapkit mlproject run no longer prints a docker run tip on every start. The suggested command pointed at the base images, which do not include chapkit, so it could not start the service.

Upgrading

No code changes required. To register a service started with chapkit mlproject run, set SERVICEKIT_ORCHESTRATOR_URL or pass --register-url. If chap-core reaches the service through a different address than the one it binds, for example a published host port, also set --advertise-host / --advertise-port (or SERVICEKIT_HOST / SERVICEKIT_PORT).

What's Changed

• chore: bump version to 2.4.0.dev0 by @mortenoh in #135
• fix: register chapkit mlproject run services with chap-core and add registration options (CLIM-1340) by @mortenoh in #136
• chore: release 2.3.1 (CLIM-1340) by @mortenoh in #137

Full Changelog: v2.3.0...v2.3.1