Registry Management
Registry Management Admin
Configure private container registries for chaos scenario images and control which groups can access them. By default, scenarios are pulled from the public Quay.io registry. Private registries enable air-gapped deployments and custom scenario images.
IMAGE parameter with its private registry URL. An image-only mirror is insufficient for signed scenario execution.This walkthrough is retained with v1.1.0 documentation and may show an earlier interface.
Creating a Private Registry
Configure a private registry by providing its connection settings (URL, credentials, TLS configuration).
Visibility
Each registry has a visibility setting that controls who can use it:
| Visibility | Description |
|---|---|
| Everyone | All users on the platform can select this registry |
| Group-based | Only users belonging to assigned groups can see and use this registry |
Impact on Scenario Selection
When a user selects a private registry during scenario execution, only the scenarios that have been mirrored to that registry will be available. Scenarios not present in the private registry will not appear in the selection list.
The Operator requires a valid signature for each selected scenario image by default. For the commands and workload-image override, see Mirror Signed Images.