Add hugo and docsy site#1127
Conversation
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: a-mccarthy The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @a-mccarthy. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
✅ Deploy Preview for dra-driver-nvidia-gpu ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
|
@shivamerla here is a PR with updated site tooling. please let me know your thoughts! :D I think there is still some work to be done around making sure the build process is right and tested. |
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
| - **ComputeDomains** (`compute-domain.nvidia.com`) — provisions ephemeral multi-node NVLink fabrics using IMEX, enabling pods on different nodes to share GPU memory at full NVLink bandwidth. | ||
|
|
||
|
|
||
| The [Kubernetes device plugin framework](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) treats hardware resources as opaque countable integers. A workload either gets a whole unit or it doesn't and there is no way to express sharing, per-workload configuration, capability constraints, or topology requirements within that model. |
There was a problem hiding this comment.
| The [Kubernetes device plugin framework](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) treats hardware resources as opaque countable integers. A workload either gets a whole unit or it doesn't and there is no way to express sharing, per-workload configuration, capability constraints, or topology requirements within that model. | |
| The [Kubernetes device plugin framework](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) treats hardware resources as opaque countable integers. A workload either gets a whole unit or nothing at all. The device plugin model does not provide a way to express sharing, per-workload configuration, capability constraints, or topology requirements. |
|
|
||
| ### GPU allocation | ||
|
|
||
| Request GPUs, MIG slices, or VFIO passthrough devices in a `ResourceClaim`, with an optional sharing strategy (time-slicing or Multi-Process Service (MPS)). |
There was a problem hiding this comment.
| Request GPUs, MIG slices, or VFIO passthrough devices in a `ResourceClaim`, with an optional sharing strategy (time-slicing or Multi-Process Service (MPS)). | |
| Request GPUs, MIG slices, or VFIO passthrough devices in a ResourceClaim, with an optional sharing strategy such as time-slicing or MPS (Multi-Process Service). |
Would be nice to avoid the nested brackets?
| description: DRA Driver components and request flows. | ||
| --- | ||
|
|
||
| This repo ships two independent Kubernetes DRA drivers from one codebase: |
There was a problem hiding this comment.
@shivamerla is there another way to frame this?
There was a problem hiding this comment.
How about something like this
gpu.nvidia.com - manages allocation of GPUs, including GPU sharing through MIG, Time-Slicing, and MPS, across both bare-metal and sandboxed environments.
compute-domain.nvidia.com - manages IMEX daemons and allocation of IMEX channel devices required for GPU memory sharing across OS domains on Multi-Node NVLink systems.
|
|
||
| VFIO (Virtual Function I/O) passes a full physical GPU directly to a container, bypassing the NVIDIA driver stack in the host kernel. This gives the container raw hardware access and is intended for workloads that manage the GPU driver themselves, such as virtual machine managers or specialized research environments. | ||
|
|
||
| VFIO passthrough has no sharing options, one container gets one GPU. |
There was a problem hiding this comment.
| VFIO passthrough has no sharing options, one container gets one GPU. | |
| VFIO passthrough has no sharing options; one container gets one GPU. |
| "postcss": "^8.4.49", | ||
| "postcss-cli": "^11.0.0" | ||
| } | ||
| } No newline at end of file |
There was a problem hiding this comment.
nit: missing newline here
|
/lgtm |
|
/release-note-none |
|
LGTM label has been added. DetailsGit tree hash: 8289181671fa8e9b07cdf3311120d0a0ca57b1b2 |
|
@a-mccarthy: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
adds website infrastructure for hugo and docsy
Which issue(s) this PR is related to:
related to #1111
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE
Additional documentation (design docs, usage docs, etc.):
Checklist
make check testpasses locallymake check-generatepasses ifapi/changed (CRDs, deepcopy, informers, listers, clientset)make check-modulespasses ifgo.mod/go.sumchangeddeployments/helm) updated if flags, RBAC, or defaults changed