Skip to main content
This page lists the KV conventions exposed by the Kernel and core services. Each entry defines what information a key represents and which component currently publishes it. For KV operations and storage behavior, see the KV storage guide.

​
Kernel service records

The Kernel publishes service metadata in the read-only sys namespace. These records let other components distinguish an available service package from a service instance that has registered with the Kernel. The catalog record describes package metadata, including the service identity, version, runtime type, contract version, command, package path, and manifest metadata. It does not indicate that the service is running. The running-instance record describes the registered instance and its routes and transports. The Kernel removes this record when the instance stops or is unloaded. A degraded instance can still have a record; the record reflects the routes and transports that were registered successfully.

​
Published application metadata

Services publish metadata under a namespace derived from the service that owns the resource. The following keys are the current conventions for resources that other services or frontend code may need to discover. The aggregate urls keys and their corresponding individual keys describe the same resource set. Use the aggregate key when discovering all resources; use an individual key when a specific resource is required.