Supporting out-of-tree drivers on OpenShift #357
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zvonkok
changed the title
openshift-ci-robot
added
the
do-not-merge/work-in-progress
|
@zshi-redhat PTAL |
openshift-ci-robot
requested review from
cgwalters,
derekwaynecarr,
dustymabe,
eparis and
fepan
eparis
reviewed
Jun 2, 2020
zshi-redhat
reviewed
Jun 3, 2020
|
/cc @darkmuggle |
darkmuggle
reviewed
Jul 7, 2020
darkmuggle
reviewed
Jul 7, 2020
darkmuggle
reviewed
Jul 7, 2020
ashcrow
reviewed
Jul 7, 2020
ashcrow
reviewed
Jul 7, 2020
ashcrow
reviewed
Jul 7, 2020
Co-authored-by: David Gray <[email protected]>
Co-authored-by: David Gray <[email protected]>
Co-authored-by: David Gray <[email protected]>
Co-authored-by: David Gray <[email protected]>
Co-authored-by: David Gray <[email protected]>
Co-authored-by: David Gray <[email protected]>
Co-authored-by: David Gray <[email protected]>
driver-toolki + kABI section added.
driver-toolki + kABI section added.
dagrayvid
reviewed
Mar 19, 2021
dagrayvid
reviewed
Mar 19, 2021
Co-authored-by: David Gray <[email protected]>
mrunalp
reviewed
Apr 22, 2021
added 7 commits
April 22, 2021 19:51
zvonkok
commented
May 5, 2021
|
@zvonkok: The following test failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
SchSeba
reviewed
May 10, 2021
| value: "SECRET_ACCESS_KEY" | ||
| driverContainer: | ||
| source: | ||
| git: |
There was a problem hiding this comment.
some of the environments that need OOT drivers are in disconnected environments will it be reasonable to add the ability to use a container image as a container for the driver source?
There was a problem hiding this comment.
See CR section artifacts: from Claim, Image or HostPath
SchSeba
reviewed
Jun 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support out-of-tree drivers on OpenShift for enabling custom hardware and third-party kernel modules on container and non-container based operating systems.
In OpenShift v3.x out-of-tree drivers could be easily installed on the nodes, since the node was a full RHEL node with a subscription and needed tools were installed easily with yum.
In OpenShift v4.x this changed with the introduction of RHCOS. There are currently two different documented ways to enable out-of-tree drivers. One way is using an SRO based operator such as the nvidia GPU operator and the other is using kmods-via-containers.
We want to come up with a unified solution that works for our customers across RHCOS and RHEL. The solution should also help customers that are currently on RHEL7 to consider moving to RHCOS which is fully managed and easier to support in OpenShift.
(As a side note we had DriverContainers running with OCP-3.11 on AtomicHost)