https://krkn-chaos.dev/tags/architecture/Recent content in Architecture on KrknHugoenhttps://krkn-chaos.dev/docs/developers-guide/scenario-architecture/Mon, 01 Jan 0001 00:00:00 +0000https://krkn-chaos.dev/docs/developers-guide/scenario-architecture/<p>A custom scenario connects two contracts: a <strong>container image contract</strong> for discovery and execution, and a <strong>Python plugin contract</strong> for the Krkn engine. The image carries the metadata needed to present a scenario to users; the plugin implements the behavior that Krkn runs.</p> <figure><a href="https://krkn-chaos.dev/images/developers-guide/scenario-lifecycle.svg"><img src="https://krkn-chaos.dev/images/developers-guide/scenario-lifecycle.svg" alt="A registry supplies image metadata to krknctl and Krkn Operator. The operator creates a scenario Pod, whose startup script turns environment variables into YAML. Krkn selects the plugin, which calls the target API through krkn-lib."></a><figcaption> <p>The same image connects discovery, configuration, and execution. Select the diagram to view it at full size.</p>