Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update top-of-tree GPU Operator OLM bundle image path #59

Conversation

wabouhamad
Copy link
Collaborator

@wabouhamad wabouhamad commented Feb 28, 2025

Updating GPU Operator OLM master bundle image path to new link:

ghcr.io/nvidia/gpu-operator/gpu-operator-bundle:main-latest

Summary by CodeRabbit

  • Documentation

    • Updated the default GPU operator bundle image reference in the README to reflect the new source from GitHub Container Registry instead of GitLab.
  • Chores

    • Standardized the default GPU operator bundle image reference across configurations for consistent deployment outcomes when using the bundle option.

Copy link
Contributor

coderabbitai bot commented Feb 28, 2025

Walkthrough

The changes update the default value for the GPU operator bundle image across the project. The new value now points to GitHub Container Registry instead of the GitLab registry. This update is applied in documentation, configuration code, and tests to ensure consistency when deploying from a bundle.

Changes

Files Change Summary
README.md, internal/deploy/deploy.go Updated default GPU bundle image value from registry.gitlab.com/nvidia/kubernetes/gpu-operator/staging/gpu-operator-bundle:main-latest to ghcr.io/nvidia/gpu-operator/gpu-operator-bundle:main-latest.
internal/deploy/deploy_test.go, tests/nvidiagpu/deploy-gpu-test.go Modified expected/default bundle image values in tests to reflect the new GitHub Container Registry endpoint.
renovate.json Updated depNameTemplate and registryUrlTemplate in regexManagers to reflect the new source registry for the GPU Operator bundle, changing from GitLab to GitHub.

Possibly related PRs

  • Adding initial renovate configuration file #58: The changes in the main PR are related to the updates of the GPU Operator bundle image source, which aligns with the modifications in the renovate.json file of the retrieved PR that also addresses the GPU Operator bundle image management.

Suggested labels

lgtm

Suggested reviewers

  • empovit

Poem

I hopped through lines of code today,
Changing images in a brand new way.
From GitLab's nest to GitHub skies,
Our bundle now in a fresh disguise.
With every test and file in view,
I celebrate the change—hop, hop, woo-hoo!
🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

  • 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.

@wabouhamad
Copy link
Collaborator Author

/cc @empovit @TomerNewman

@openshift-ci openshift-ci bot requested a review from TomerNewman February 28, 2025 21:45
Copy link
Contributor

@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)
README.md (1)

76-76: Correctly updated the GPU Operator bundle image path

The default value for NVIDIAGPU_BUNDLE_IMAGE has been updated to use GitHub Container Registry instead of GitLab registry, which aligns with the PR objective.

For consistency with other list items in the document, consider using an asterisk (*) instead of a dash (-) for this bullet point.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

76-76: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 74b4864 and 34c58a8.

📒 Files selected for processing (4)
  • README.md (1 hunks)
  • internal/deploy/deploy.go (1 hunks)
  • internal/deploy/deploy_test.go (1 hunks)
  • tests/nvidiagpu/deploy-gpu-test.go (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • tests/nvidiagpu/deploy-gpu-test.go
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md

76-76: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)

🔇 Additional comments (2)
internal/deploy/deploy_test.go (1)

33-33: Updated test expectation to match the new default bundle image path

The test has been properly updated to expect the new GitHub Container Registry path, ensuring consistency with the implementation.

internal/deploy/deploy.go (1)

20-20: Updated default bundle image path in BundleConfig struct

The default value for the GPU Operator bundle image has been changed from GitLab registry to GitHub Container Registry, which properly implements the PR objective.

Copy link
Member

@TomerNewman TomerNewman left a comment

Choose a reason for hiding this comment

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

Can you also change in renovate.json? :)

@empovit
Copy link
Member

empovit commented Mar 2, 2025

/test

Copy link

openshift-ci bot commented Mar 2, 2025

@empovit: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test 4.12-images
/test 4.12-nvidia-gpu-operator-e2e-latest
/test 4.12-stable-images
/test 4.12-stable-nvidia-gpu-operator-e2e-24-6-x
/test 4.12-stable-nvidia-gpu-operator-e2e-24-9-x
/test 4.12-stable-nvidia-gpu-operator-e2e-master
/test 4.14-images
/test 4.14-nvidia-gpu-operator-e2e-latest
/test 4.14-stable-images
/test 4.14-stable-nvidia-gpu-operator-e2e-24-6-x
/test 4.14-stable-nvidia-gpu-operator-e2e-24-9-x
/test 4.14-stable-nvidia-gpu-operator-e2e-master
/test 4.15-images
/test 4.15-nvidia-gpu-operator-e2e-latest
/test 4.15-stable-images
/test 4.15-stable-nvidia-gpu-operator-e2e-24-6-x
/test 4.15-stable-nvidia-gpu-operator-e2e-24-9-x
/test 4.15-stable-nvidia-gpu-operator-e2e-master
/test 4.16-images
/test 4.16-nvidia-gpu-operator-e2e-latest
/test 4.16-stable-images
/test 4.16-stable-nvidia-gpu-operator-e2e-24-6-x
/test 4.16-stable-nvidia-gpu-operator-e2e-24-9-x
/test 4.16-stable-nvidia-gpu-operator-e2e-master
/test 4.17-images
/test 4.17-nvidia-gpu-operator-e2e-latest
/test 4.17-stable-images
/test 4.17-stable-nvidia-gpu-operator-e2e-24-6-x
/test 4.17-stable-nvidia-gpu-operator-e2e-24-9-x
/test 4.17-stable-nvidia-gpu-operator-e2e-master
/test 4.18-images
/test 4.18-nvidia-gpu-operator-e2e-cutting-edge
/test 4.18-stable-images
/test 4.18-stable-nvidia-gpu-operator-e2e-24-6-x
/test 4.18-stable-nvidia-gpu-operator-e2e-24-9-x
/test 4.18-stable-nvidia-gpu-operator-e2e-master
/test images
/test lint

Use /test all to run the following jobs that were automatically triggered:

pull-ci-rh-ecosystem-edge-nvidia-ci-main-images
pull-ci-rh-ecosystem-edge-nvidia-ci-main-lint

In response to this:

/test

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.

@empovit
Copy link
Member

empovit commented Mar 2, 2025

/test 4.18-stable-nvidia-gpu-operator-e2e-master

@empovit
Copy link
Member

empovit commented Mar 2, 2025

The rehearsal job was OK

I0302 10:32:40.866523 13380 deploy-gpu-test.go:174] env variable NVIDIAGPU_BUNDLE_IMAGE is not set, will use the default bundle image 'ghcr.io/nvidia/gpu-operator/gpu-operator-bundle:main-latest'

@wabouhamad could you please fix the Renovate file as @TomerNewman has suggested, and we'll merge the PR? No need to re-test.

nvidia-ci/renovate.json

Lines 12 to 15 in 74b4864

"datasourceTemplate": "docker",
"depNameTemplate": "registry.gitlab.com/nvidia/kubernetes/gpu-operator/staging/gpu-operator-bundle",
"currentValueTemplate": "main-latest",
"registryUrlTemplate": "https://registry.gitlab.com"

Updating GPU Operator OLM master bundle image path to new link:

ghcr.io/nvidia/gpu-operator/gpu-operator-bundle:main-latest
@wabouhamad wabouhamad force-pushed the gpu-bundle-path-update-2025-02-28 branch from 34c58a8 to 21ab644 Compare March 3, 2025 05:37
@wabouhamad
Copy link
Collaborator Author

@TomerNewman @empovit

The rehearsal job was OK

I0302 10:32:40.866523 13380 deploy-gpu-test.go:174] env variable NVIDIAGPU_BUNDLE_IMAGE is not set, will use the default bundle image 'ghcr.io/nvidia/gpu-operator/gpu-operator-bundle:main-latest'

@wabouhamad could you please fix the Renovate file as @TomerNewman has suggested, and we'll merge the PR? No need to re-test.

nvidia-ci/renovate.json

Lines 12 to 15 in 74b4864

"datasourceTemplate": "docker",
"depNameTemplate": "registry.gitlab.com/nvidia/kubernetes/gpu-operator/staging/gpu-operator-bundle",
"currentValueTemplate": "main-latest",
"registryUrlTemplate": "https://registry.gitlab.com"

Done.

@wabouhamad
Copy link
Collaborator Author

@TomerNewman @empovit PTAL, updated the renovate.json file.

Copy link
Contributor

@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)
README.md (1)

76-76: Update of GPU Operator bundle image default value and minor formatting tweaks.
The new default value for NVIDIAGPU_BUNDLE_IMAGE is correctly updated to
ghcr.io/nvidia/gpu-operator/gpu-operator-bundle:main-latest, which aligns with the new registry source.
Note: There is a small typo in the description text ("bundlle" should be "bundle"). Also, markdownlint suggests using asterisks (*) instead of dashes for unordered list items. Consider updating the bullet style if consistency is desired.

Diff suggestion for typo fix:

- ghcr.io/nvidia/gpu-operator/gpu-operator-bundle:main-latest - _optional when deploying from bundlle_
+ ghcr.io/nvidia/gpu-operator/gpu-operator-bundle:main-latest - _optional when deploying from bundle_
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

76-76: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 34c58a8 and 21ab644.

📒 Files selected for processing (5)
  • README.md (1 hunks)
  • internal/deploy/deploy.go (1 hunks)
  • internal/deploy/deploy_test.go (1 hunks)
  • renovate.json (1 hunks)
  • tests/nvidiagpu/deploy-gpu-test.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • internal/deploy/deploy.go
  • tests/nvidiagpu/deploy-gpu-test.go
  • internal/deploy/deploy_test.go
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md

76-76: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)

🔇 Additional comments (2)
renovate.json (2)

13-13: Correct update of depNameTemplate.
The depNameTemplate is now set to "ghcr.io/nvidia/gpu-operator/gpu-operator-bundle", replacing the previous GitLab-based value. This ensures that the Renovate configuration points to the new GitHub Container Registry.


15-15: Correct update of registryUrlTemplate.
The registryUrlTemplate is updated to "https://ghcr.io", consistent with the new bundle image source. This change matches the intended shift from GitLab to GitHub Container Registry.

@empovit
Copy link
Member

empovit commented Mar 3, 2025

/lgtm
/approve

Copy link

openshift-ci bot commented Mar 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: empovit, wabouhamad

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

The pull request process is described here

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-merge-bot openshift-merge-bot bot merged commit 2d37c74 into rh-ecosystem-edge:main Mar 3, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants