ocpvirt-rhel9-imagelisted
Install: claude install-skill ericcames/sales.demos
# ocpvirt-rhel9-image
Links an environment to the published RHEL 9 CIS L1 hardened golden image.
Takes about **2 minutes** for the cron to import and the DataSource to report
Ready.
This skill contains **no logic**. All the work is in
[`playbooks/link_rhel9_image.yml`](../../../playbooks/link_rhel9_image.yml).
## What it does
1. Reads the HyperConverged CR and asserts CNV is installed.
2. Adds a `rhel9-cis-l1-image-cron` DataImportCron template to the
HyperConverged CR, pointing at the containerdisk in `quay_rhel9_image`.
3. Waits for the `rhel9-cis-l1` DataSource to report `Ready=True`.
4. Verifies the backing volume (VolumeSnapshot or PVC) is usable.
5. Reports the result.
## This is the consumer half. It does not build anything.
| | Owns |
|---|---|
| **This skill** | Pointing a cluster at the published image |
| The producer (`ericcames/image.builder.pipeline`) | Building and publishing the containerdisk |
The contract between them is one string: `quay_rhel9_image` in
`inventory/group_vars/<env>/connection.yml`. The playbook asserts it is
non-empty and rejects placeholder values.
## No pull secret needed
The quay repository is **public** (#208), so CDI pulls the image without
credentials. This is the key difference from the Windows twin
(`ocpvirt-windows-image`), which needs a pull secret because Windows media
cannot be redistributed publicly.
## Why a separate DataSource
The stock `rhel9` DataSource is managed by CNV's built-in DataImportCron, which
pulls t