CNV-83484: Remove custom ConfigMap config from vgpuDeviceManager examples - #118671
CNV-83484: Remove custom ConfigMap config from vgpuDeviceManager examples#118671abrennan89 wants to merge 1 commit into
Conversation
…ples The vgpuDeviceManager config block referenced a custom ConfigMap that users were never told how to create, causing the NVIDIA GPU Operator to skip ConfigMap creation and leaving vGPU non-functional. Removing the config block lets the operator manage the ConfigMap automatically. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@abrennan89: This pull request references CNV-83484 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 bug to target the "5.1.0" version, but no target version was set. DetailsIn response to this:
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. |
|
@abrennan89: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Jira: https://redhat.atlassian.net/browse/CNV-83484
Preview link: TBA
Versions: 4.21+ (confirm)
Summary
ConfigMapconfigblock fromvgpuDeviceManagerin two GPU operator YAML examples (about-using-gpu-operator.adocandrdma-configuring-the-gpu-operator.adoc).ConfigMap(vgpu-devices-config) that users were never told how to create, causing the NVIDIA GPU Operator to skipConfigMapcreation and leaving vGPU non-functional.ConfigMapautomatically is the correct default behavior.🤖 Generated with Claude Code