Skip to content

ROSAENG-62357: Update CI for rosa-hyperfleet-api monorepo#82371

Open
typeid wants to merge 1 commit into
openshift:mainfrom
typeid:api_update
Open

ROSAENG-62357: Update CI for rosa-hyperfleet-api monorepo#82371
typeid wants to merge 1 commit into
openshift:mainfrom
typeid:api_update

Conversation

@typeid

@typeid typeid commented Jul 23, 2026

Copy link
Copy Markdown
Member

Summary

  • Updates CI config for rosa-hyperfleet-api after monorepo consolidation (ROSAENG-62357: Consolidate hyperfleet-operator + hyperfleet-db into -api openshift-online/rosa-hyperfleet-api#169)
  • Builds two images: platform-api (from platform-api/Dockerfile) and hyperfleet-operator (from hyperfleet-operator/Dockerfile)
  • Adds postsubmit image push for hyperfleet-operator to quay.io
  • Renames e2e job from rosa-regionality-compatibility-e2e to on-demand-e2e
  • Adds multi-component image push and helm override support for ephemeral e2e workflow
  • Adds integration test job with nested_podman capability for tests that spin up Postgres/DynamoDB containers via podman

Test plan

  • CI lint/unit/verify jobs pass on rosa-hyperfleet-api PRs
  • Integration tests run with nested podman privileges
  • Both platform-api and hyperfleet-operator images build in CI
  • Postsubmit pushes both images to quay.io
  • /test on-demand-e2e triggers ephemeral e2e with both component images

🤖 Generated with Claude Code

Summary by CodeRabbit

Updates the rosa-hyperfleet-api OpenShift CI configuration to build and publish separate platform-api and hyperfleet-operator images. Adds postsubmit pushes, nested-Podman integration testing, and renames the ephemeral e2e workflow to on-demand-e2e.

Extends image-push and provisioning steps to support multiple component images, including per-component Quay destinations and Helm repository/tag overrides for ephemeral environments.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 23, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

@typeid: This pull request references ROSAENG-62357 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Update CI config, image push, and ephemeral e2e workflow to support the consolidated monorepo structure with separate platform-api and hyperfleet-operator images. Adds multi-component image push and helm override support.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@typeid typeid changed the title ROSAENG-62357: Update CI for rosa-hyperfleet-api monorepo consolidation ROSAENG-62357: Update CI for rosa-hyperfleet-api monorepo Jul 23, 2026
@openshift-ci
openshift-ci Bot requested review from cdoan1 and psav July 23, 2026 17:52
@openshift-ci

openshift-ci Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: typeid

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 23, 2026
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 3711ef1c-b827-4e5f-9f03-b855b20af20e

📥 Commits

Reviewing files that changed from the base of the PR and between 6f57549 and 9e28e8a.

⛔ Files ignored due to path filters (2)
  • ci-operator/jobs/openshift-online/rosa-hyperfleet-api/openshift-online-rosa-hyperfleet-api-main-postsubmits.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift-online/rosa-hyperfleet-api/openshift-online-rosa-hyperfleet-api-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (6)
  • ci-operator/config/openshift-online/rosa-hyperfleet-api/openshift-online-rosa-hyperfleet-api-main.yaml
  • ci-operator/step-registry/rosa-hyperfleet/ephemeral-e2e/rosa-hyperfleet-ephemeral-e2e-workflow.yaml
  • ci-operator/step-registry/rosa-hyperfleet/image-push/rosa-hyperfleet-image-push-commands.sh
  • ci-operator/step-registry/rosa-hyperfleet/image-push/rosa-hyperfleet-image-push-ref.yaml
  • ci-operator/step-registry/rosa-hyperfleet/provision/rosa-hyperfleet-provision-commands.sh
  • ci-operator/step-registry/rosa-hyperfleet/provision/rosa-hyperfleet-provision-ref.yaml
🚧 Files skipped from review as they are similar to previous changes (6)
  • ci-operator/step-registry/rosa-hyperfleet/ephemeral-e2e/rosa-hyperfleet-ephemeral-e2e-workflow.yaml
  • ci-operator/step-registry/rosa-hyperfleet/image-push/rosa-hyperfleet-image-push-ref.yaml
  • ci-operator/step-registry/rosa-hyperfleet/provision/rosa-hyperfleet-provision-commands.sh
  • ci-operator/step-registry/rosa-hyperfleet/provision/rosa-hyperfleet-provision-ref.yaml
  • ci-operator/step-registry/rosa-hyperfleet/image-push/rosa-hyperfleet-image-push-commands.sh
  • ci-operator/config/openshift-online/rosa-hyperfleet-api/openshift-online-rosa-hyperfleet-api-main.yaml

Walkthrough

The CI workflow now builds and publishes separate platform-api and hyperfleet-operator images, supports extra image publishing, and applies corresponding Helm overrides during ephemeral provisioning.

Changes

ROSA Hyperfleet multi-image CI flow

Layer / File(s) Summary
Component image builds and job wiring
ci-operator/config/openshift-online/rosa-hyperfleet-api/..., ci-operator/step-registry/rosa-hyperfleet/ephemeral-e2e/...
CI builds separate component images, adds integration testing, publishes images through distinct jobs, and passes both images to on-demand E2E workflows.
Primary and extra image publishing
ci-operator/step-registry/rosa-hyperfleet/image-push/*
The image-push step conditionally publishes the primary image and configured extra component images with CI and postsubmit tags.
Extra component provisioning overrides
ci-operator/step-registry/rosa-hyperfleet/provision/*
Provisioning generates extra component Helm overrides and substitutes image repository and tag placeholders before ephemeral provisioning.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant CIJobs as CI jobs
  participant ImagePush as rosa-hyperfleet-image-push
  participant Quay
  participant Provision as rosa-hyperfleet-provision

  CIJobs->>ImagePush: Provide platform-api and hyperfleet-operator images
  ImagePush->>Quay: Mirror primary and extra images
  ImagePush->>Provision: Write component image override
  Provision->>Provision: Generate and apply Helm overrides
Loading

Possibly related PRs

  • openshift/release#82419: Updates the same ROSA Hyperfleet CI workflow’s image build and promotion configuration.

Suggested labels: lgtm

Suggested reviewers: psav, cdoan1

🚥 Pre-merge checks | ✅ 13 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Ipv6 And Disconnected Network Test Compatibility ⚠️ Warning FAIL: the new on-demand-e2e workflow still clones from GitHub and pushes/pulls via quay.io, so it isn't disconnected-safe and no IPv6/disconnected skip is added. Mirror GitHub/quay dependencies internally or add [Skipped:Disconnected]/IP-family detection so the job avoids public internet in IPv6-only runs.
✅ Passed checks (13 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title is concise and accurately summarizes the main change: CI updates for the rosa-hyperfleet-api monorepo.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed Changed files are CI config and step scripts only; no Ginkgo It/Describe/Context/When test titles were added or modified.
Test Structure And Quality ✅ Passed No Ginkgo test code changed in this PR—only CI/job YAML and shell step scripts—so the test-structure quality check is not applicable.
Microshift Test Compatibility ✅ Passed PASS: The PR only changes CI config and step scripts; no new Go/Ginkgo tests, MicroShift guards, or unavailable OpenShift API/resource references were added.
Single Node Openshift (Sno) Test Compatibility ✅ Passed No new Ginkgo e2e tests were added in the touched files, and the new jobs only adjust CI plumbing/image handling.
Topology-Aware Scheduling Compatibility ✅ Passed Touched files are CI config and step scripts only; no pod affinity, node selectors, replica logic, or topology-sensitive workload scheduling was added.
Ote Binary Stdout Contract ✅ Passed PR only changes CI YAML and step shell scripts; no OTE binary main/init/TestMain/suite-setup stdout writes were added.
No-Weak-Crypto ✅ Passed No MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret/token comparisons were added in the changed files.
Container-Privileges ✅ Passed No added manifest contains privileged/hostPID/hostNetwork/hostIPC/SYS_ADMIN/allowPrivilegeEscalation; only nested-podman labels and a build-image USER root line appear.
No-Sensitive-Data-In-Logs ✅ Passed No new logging of secrets/PII; added echoes only print image refs, repo names, target paths, and SHAs.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/step-registry/rosa-hyperfleet/ephemeral-e2e/rosa-hyperfleet-ephemeral-e2e-workflow.yaml`:
- Line 22: Update the on-demand-e2e example configuration to document all
required multi-component inputs, including CI_COMPONENT_IMAGE,
CI_OPERATOR_IMAGE, and ROSA_REGIONAL_EXTRA_COMPONENTS, so it demonstrates the
operator override flow.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 17390362-f6d8-4a39-b595-ffcc5fc71bcc

📥 Commits

Reviewing files that changed from the base of the PR and between c19d1eb and 6f57549.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift-online/rosa-hyperfleet-api/openshift-online-rosa-hyperfleet-api-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (6)
  • ci-operator/config/openshift-online/rosa-hyperfleet-api/openshift-online-rosa-hyperfleet-api-main.yaml
  • ci-operator/step-registry/rosa-hyperfleet/ephemeral-e2e/rosa-hyperfleet-ephemeral-e2e-workflow.yaml
  • ci-operator/step-registry/rosa-hyperfleet/image-push/rosa-hyperfleet-image-push-commands.sh
  • ci-operator/step-registry/rosa-hyperfleet/image-push/rosa-hyperfleet-image-push-ref.yaml
  • ci-operator/step-registry/rosa-hyperfleet/provision/rosa-hyperfleet-provision-commands.sh
  • ci-operator/step-registry/rosa-hyperfleet/provision/rosa-hyperfleet-provision-ref.yaml

Usage from a CI config:
tests:
- as: rosa-regionality-compatibility-e2e
- as: on-demand-e2e

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Document the second component dependency.

The example only supplies CI_COMPONENT_IMAGE; copying it will not provide CI_OPERATOR_IMAGE or ROSA_REGIONAL_EXTRA_COMPONENTS, so the new operator override flow is omitted. Update the example to show the multi-component inputs.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/step-registry/rosa-hyperfleet/ephemeral-e2e/rosa-hyperfleet-ephemeral-e2e-workflow.yaml`
at line 22, Update the on-demand-e2e example configuration to document all
required multi-component inputs, including CI_COMPONENT_IMAGE,
CI_OPERATOR_IMAGE, and ROSA_REGIONAL_EXTRA_COMPONENTS, so it demonstrates the
operator override flow.

Update CI config, image push, and ephemeral e2e workflow to support the
consolidated monorepo structure with separate platform-api and hyperfleet-operator
images. Adds multi-component image push and helm override support.

Add integration test job with nested_podman capability for tests that
need to run Postgres/DynamoDB containers via podman.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@typeid: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-online-rosa-hyperfleet-api-main-integration openshift-online/rosa-hyperfleet-api presubmit Presubmit changed
pull-ci-openshift-online-rosa-hyperfleet-api-main-on-demand-e2e openshift-online/rosa-hyperfleet-api presubmit Presubmit changed
pull-ci-openshift-online-rosa-hyperfleet-api-main-images openshift-online/rosa-hyperfleet-api presubmit Ci-operator config changed
pull-ci-openshift-online-rosa-hyperfleet-api-main-lint openshift-online/rosa-hyperfleet-api presubmit Ci-operator config changed
pull-ci-openshift-online-rosa-hyperfleet-api-main-unit openshift-online/rosa-hyperfleet-api presubmit Ci-operator config changed
pull-ci-openshift-online-rosa-hyperfleet-api-main-verify openshift-online/rosa-hyperfleet-api presubmit Ci-operator config changed
periodic-ci-openshift-online-rosa-hyperfleet-main-nightly-ephemeral N/A periodic Registry content changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@typeid: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants