Skip to content

Commit

Permalink
Specify namespace when getting GPU driver upgrade events (#133)
Browse files Browse the repository at this point in the history
Events are namespace-scoped. The GPUDriverUpgrade events are associated with Node
objects and are emitted in the default namespace. This aligns with the Node events
generated by the kubelet, which also show up in the default namespace.

Signed-off-by: Christopher Desiniotis <[email protected]>
  • Loading branch information
cdesiniotis authored Dec 3, 2024
1 parent fa4b34f commit 49af9fb
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions gpu-operator/gpu-driver-upgrades.rst
Original file line number Diff line number Diff line change
Expand Up @@ -219,7 +219,7 @@ Below are an example set of events generated for the upgrade of one node.

.. code-block:: console
$ kubectl get events --sort-by='.lastTimestamp' | grep GPUDriverUpgrade
$ kubectl get events -n default --sort-by='.lastTimestamp' | grep GPUDriverUpgrade
*Example Output*

Expand Down Expand Up @@ -259,7 +259,7 @@ If the upgrade fails for a particular node, the node is labelled with the ``upgr

.. code:: console
$ kubectl get events --sort-by='.lastTimestamp' | grep GPUDriverUpgrade
$ kubectl get events -n default --sort-by='.lastTimestamp' | grep GPUDriverUpgrade
#. (Optional) Check the logs from the upgrade controller in the gpu-operator container:

Expand Down

0 comments on commit 49af9fb

Please sign in to comment.