Skip to content

Commit

Permalink
fixed a minor indentation issue
Browse files Browse the repository at this point in the history
  • Loading branch information
pappasilenus committed Mar 11, 2019
1 parent e12eec3 commit 801bc82
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/cookbook/gpus.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Pachyderm currently supports GPUs through Kubernetes device plugins. If you already have a GPU enabled Kubernetes cluster through device plugins, then skip to [Using GPUs in Pipelines](gpus.html#using-gpus-in-pipelines).

# Setting up a GPU Enabled Kubernetes Cluster
## Setting up a GPU Enabled Kubernetes Cluster

For guidance on how to set up a GPU enabled Kubernetes cluster through device plugins, refer to the Kubernetes [docs](https://kubernetes.io/docs/tasks/manage-gpus/scheduling-gpus/).

Expand All @@ -12,7 +12,7 @@ Setting up a GPU enabled Kubernetes cluster can be a difficult process depending
2. Kubernetes is exposing the GPU resources. This can be checked by describing the GPU nodes with `kubectl describe node`. You should see the GPU resources marked as allocatable/scheduleable if they are setup properly.
3. Your application/framework can access and use the GPUs. This may be as simple as making shared libraries accesible by the application/framework running in your container. Which can be done by baking environment variables into the Docker image or passing in environment variables through the pipeline spec.

# Using GPUs in Pipelines
## Using GPUs in Pipelines

If you already have a GPU enabled Kubernetes cluster through device plugins, then using GPUs in your pipelines is as simple as setting up a GPU resource limit with the type and number of GPUs. An example pipeline spec for a GPU enabled pipeline is as follows:

Expand Down

0 comments on commit 801bc82

Please sign in to comment.