(env_op_images): Document workflow, variables, and pulled/verified report behavior#3898
Conversation
…port behavior Replace the short summary with a full description of the role: operator image collection, ICSP/IDMS-based pulled-images reporting, and optional CRI-O journal verification. Document the kubeconfig requirement, the three-step workflow with task file pointers, and align parameter defaults with the role (including dryrun and pulled-report namespaces). Adding sections that explain how the pulled report derives expected_pull_* from pod status image strings vs. imageID, and how the verified report adds digest-matched CRI-O evidence fields. Signed-off-by: nemarjan <nemarjan@redhat.com>
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 48m 00s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 37m 20s |
|
recheck |
|
Build failed (check pipeline). Post ❌ openstack-k8s-operators-content-provider TIMED_OUT in 31m 25s |
1 participant
Replace the short summary with a full description of the role: operator image collection, ICSP/IDMS-based pulled-images reporting, and optional CRI-O journal verification.
Document the kubeconfig requirement, the three-step workflow with task file pointers, and align parameter defaults with the role (including dryrun and pulled-report namespaces). Adding sections that explain how the pulled report derives expected_pull_* from pod status image strings vs. imageID, and how the verified report adds digest-matched CRI-O evidence fields.