Add Google driver information, small fixups #45
Conversation
Signed-off-by: John Belamaric <jbelamaric@google.com>
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johnbelamaric The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
approved
|
/assign @pohly |
| | FuriosaAI | could not find | ||
| | Google (NVIDIA GPU) | Via NVIDIA's driver ([docs for GKE 1.32-1.34](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/about-dynamic-resource-allocation)) | ||
| | Google (TPU) | [Docs for GKE 1.32-1.34](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/about-dynamic-resource-allocation) | ||
| | Google (DRANET) | [DRANET Site](https://dranet.dev), [GKE Docs](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/allocate-network-resources-dra) |
There was a problem hiding this comment.
Not directly related to this PR, just wondering how to document it:
Who owns dranet.dev? What will happen with that URL when dranet moves to the CNCF and then Kubernetes? Should we add a link to the on-going transfer to the CNCF? Does someone have the link for the issue that was created at KubeCon?
As I mentioned to @aojea already, it would be better if the attributes published by dranet used a vendor-controlled domain (like this dranet.dev) instead of dra.net, but I guess it is too late to fix this.
/cc @aojea @LionelJouin
3 participants
No description provided.