Skip to content

AGENT-1260: Switch to rhel-9-base-nodejs-openshift base image#3124

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
rwsu:AGENT-1260-use-rhel-9-base-nodejs-image
Aug 19, 2025
Merged

AGENT-1260: Switch to rhel-9-base-nodejs-openshift base image#3124
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
rwsu:AGENT-1260-use-rhel-9-base-nodejs-image

Conversation

@rwsu
Copy link
Contributor

@rwsu rwsu commented Aug 19, 2025

For nodejs builds switch image from nodejs-18-minimal.

Summary by CodeRabbit

  • Chores
    • Updated the UI build container to a newer, supported base image, improving consistency with platform standards and enabling up-to-date dependencies.
    • Removed unnecessary build tools from the image to streamline builds and reduce the attack surface.
    • Improves security posture and build reliability without altering user-facing functionality.
    • No changes to application features or behavior are expected for end users.

For nodejs builds switch image from nodejs-18-minimal.
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 19, 2025

@rwsu: This pull request references AGENT-1260 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 sub-task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

For nodejs builds switch image from nodejs-18-minimal.

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 19, 2025
@openshift-ci openshift-ci bot requested review from celdrake and jgyselov August 19, 2025 01:32
@coderabbitai
Copy link

coderabbitai bot commented Aug 19, 2025

Walkthrough

Updated the UI build stage base image in apps/assisted-disconnected-ui/Containerfile.ocp and removed the microdnf installation of rsync and git. No other lines changed and no public/exported declarations were affected.

Changes

Cohort / File(s) Summary
Containerfile base image update
apps/assisted-disconnected-ui/Containerfile.ocp
Switched ui-build base image to registry.ci.openshift.org/ocp/builder:rhel-9-base-nodejs-openshift-4.19 and removed RUN microdnf install -y rsync git; rest unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I nudge my nose at Docker’s brew,
A fresher base, a lighter stew.
No rsync snacks, no git to chew—
Just hopping builds, sleek and new.
Thump-thump! The pipelines hum,
Carrots compiled—deployments come. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

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

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@openshift-ci
Copy link

openshift-ci bot commented Aug 19, 2025

Hi @rwsu. Thanks for your PR.

I'm waiting for a openshift-assisted member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@openshift-ci openshift-ci bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 19, 2025
@rwsu
Copy link
Contributor Author

rwsu commented Aug 19, 2025

/cc @rawagner

@openshift-ci openshift-ci bot requested a review from rawagner August 19, 2025 01:33
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 19, 2025

@rwsu: This pull request references AGENT-1260 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 sub-task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

For nodejs builds switch image from nodejs-18-minimal.

Summary by CodeRabbit

  • Chores
  • Updated the UI build container to a newer, supported base image, improving consistency with platform standards and enabling up-to-date dependencies.
  • Removed unnecessary build tools from the image to streamline builds and reduce the attack surface.
  • Improves security posture and build reliability without altering user-facing functionality.
  • No changes to application features or behavior are expected for end users.

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
apps/assisted-disconnected-ui/Containerfile.ocp (1)

1-1: Optional: parameterize the OCP minor to avoid duplication and ease future bumps.

You reference 4.19 in two FROMs (Node and Go). Consider a single ARG for the OCP minor to keep them in sync and simplify future upgrades. Also consider pinning to image digests for supply-chain stability.

Example:

  • Add at the top:
    ARG OCP_MINOR=4.19

  • Then:
    FROM registry.ci.openshift.org/ocp/builder:rhel-9-base-nodejs-openshift-${OCP_MINOR} AS ui-build
    ...
    FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.23-openshift-${OCP_MINOR} as proxy-build

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 2f66f10 and e669839.

📒 Files selected for processing (1)
  • apps/assisted-disconnected-ui/Containerfile.ocp (1 hunks)
🔇 Additional comments (3)
apps/assisted-disconnected-ui/Containerfile.ocp (3)

1-1: LGTM on switching to the OCP NodeJS builder (pinned to 4.19).

This change improves alignment with OCP builder images and removes the need for manual package installs. Tag pinning (vs latest) is appreciated.


1-1: Double-check target version alignment (4.19 vs. CI bot’s note about 4.20).

CI noted the JIRA target version should be 4.20.0. If that’s a release targeting requirement (not just a ticket field), consider switching the base image(s) to the 4.20 stream. If 4.19 is intentional, ignore.


1-1: Manual verification required: ensure tooling in the new base image

The check script failed because neither podman nor docker is installed locally. To prevent CI build failures, please install one of these runtimes and re‐run the following in your environment:

#!/usr/bin/env bash
set -euo pipefail
IMAGE="registry.ci.openshift.org/ocp/builder:rhel-9-base-nodejs-openshift-4.19"
RUNTIME="$(command -v podman || command -v docker)"
$RUNTIME run --rm --entrypoint /bin/sh "$IMAGE" -lc '
  echo "node:     $(node -v 2>/dev/null || echo missing)"
  echo "npm:      $(npm -v 2>/dev/null || echo missing)"
  echo "git:      $(git --version 2>/dev/null || echo missing)"
  echo "corepack: $(corepack --version 2>/dev/null || echo missing)"
'

Verify the image reports versions (not “missing”) for:

  • node
  • npm
  • git
  • corepack

If any are missing, add microdnf install -y <tool> back into the Containerfile.

@celdrake
Copy link
Contributor

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 19, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2025
@openshift-ci
Copy link

openshift-ci bot commented Aug 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: celdrake, rwsu

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 Aug 19, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 8071f75 into openshift-assisted:master Aug 19, 2025
11 checks passed
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. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants