-
Notifications
You must be signed in to change notification settings - Fork 90
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
gpu-cluster: Remove step to create gpu-operator
ns
#173
base: main
Are you sure you want to change the base?
Conversation
- Remove trailing whitespaces. - Remove unused links. Signed-off-by: Suraj Deshmukh <[email protected]>
The daemonset is deployed in the `kube-system` namespace and not in the `gpu-operator` namespace. The step to create the `gpu-operator` namespace is not required. Signed-off-by: Suraj Deshmukh <[email protected]>
@surajssd : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit df1330f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Conflict with: #138 I believe this still needs to be installed in a separated namespace as this is 3rd-party plugin. Detailed counterargument is in PR 138. |
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
The daemonset is deployed in the
kube-system
namespace and not in thegpu-operator
namespace. The step to create thegpu-operator
namespace is not required.