Skip to content

[release-0.18] Enable gds, gdrcopy and mofed flags by default#1585

Closed
github-actions[bot] wants to merge 1 commit intorelease-0.18from
backport-1550-to-release-0.18
Closed

[release-0.18] Enable gds, gdrcopy and mofed flags by default#1585
github-actions[bot] wants to merge 1 commit intorelease-0.18from
backport-1550-to-release-0.18

Conversation

@github-actions
Copy link
Copy Markdown

🤖 Automated backport of #1550 to release-0.18

✅ Cherry-pick completed successfully with no conflicts.

Original PR: #1550
Original Author: @rahulait

Cherry-picked commits (1):

  • 0af9b62 change default value for gds, gdrcopy and mofed flags

This backport was automatically created by the backport bot.

With this change, we now always try to dynamically detect if the drivers are present or not.
Current code takes care of failure cases to fail-safe and we are leveraging that
for dynamic driver detection.

Signed-off-by: Rahul Sharma <[email protected]>
(cherry picked from commit 0af9b62)
@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot Bot commented Jan 15, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@elezar
Copy link
Copy Markdown
Member

elezar commented Jan 19, 2026

@rahulait was this something that we wanted to backport, or are we ok with the changes only being available in the v0.19.0 release?

@elezar elezar requested a review from rahulait January 19, 2026 12:17
@rahulait
Copy link
Copy Markdown
Contributor

rahulait commented Jan 20, 2026

We want these in gpu-operator v26.3.0 and later only. So if release-0.18 is only for v25.10.XX releases of gpu-operator, then we don't want this. If release-0.19 is going to be for gpu-operator v26.3.XX release, then we don't need this backport PR.

@elezar
Copy link
Copy Markdown
Member

elezar commented Jan 22, 2026

OK. Let's close this then. We can always reopen / create the backport again if required.

@elezar elezar closed this Jan 22, 2026
@elezar elezar deleted the backport-1550-to-release-0.18 branch January 22, 2026 11:59
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.

2 participants