Menu
Provision a VM on Red Hat Beaker for multi-arch testing
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Clone a repo with working hermetic builds and compare the implementation against the hermeto guide to identify gaps and improvements
Run check-payload locally to scan container images for FIPS compliance issues before they block a Konflux release
Run Conforma (Enterprise Contract) validation against a Konflux snapshot or a single image to check release policy compliance
Create a temporary pull request PipelineRun from an existing push PipelineRun to test build changes on an RHOAI release branch
Deploy locally-working hermetic build configuration into Konflux pipelines for RHOAI components
Productize an upstream Dockerfile for Konflux builds — base image swaps, digest pinning, FIPS compliance, label metadata, and build-arg simplification
| name | beaker-vm |
| description | Provision a VM on Red Hat Beaker for multi-arch testing |
| version | 1.0.0 |
Read guides/beaker-vm.md (relative to the plugin root) thoroughly before starting. It is the source of truth for all Beaker details — do not duplicate its content, reference it as you go.
Note: This skill is specific to the internal Red Hat Beaker system and requires Red Hat Kerberos credentials and VPN access. Confirm the user has these before proceeding.
Determine requirements: Ask the user what architecture they need (x86_64, aarch64, ppc64le, s390x) and what they plan to use the machine for. Ask if they have a distro preference (default to RHEL 9).
Check prerequisites: Confirm the user has Kerberos credentials and VPN access. Check if they have the bkr CLI configured — if not, walk them through the "Setup" section in the guide for their platform.
Provision the machine: Follow the "Provision a machine" section in the guide. Always start with --dry-run --pretty-xml so the user can review before submitting. Ask if they need packages pre-installed (e.g., git, podman, rsync) and use --ks-append if so. Ask about memory or disk requirements if relevant.
Monitor and connect: Follow the "Monitoring your job" section in the guide. Help the user watch the job and retrieve the hostname once provisioned.
Next steps: If the user is provisioning for hermetic build testing, point them to the "Testing on Remote Architectures" section in guides/hermeto-prefetch.md.
