Skip to content
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.

Sign up for GitHub

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

Instructions on setting up dynamic volume provisioner #1040

Merged
merged 6 commits into from
Aug 9, 2019
Merged

Instructions on setting up dynamic volume provisioner #1040

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
e3f3ad0
Instructions on setting up dynamic volume provisioner
krishnadurai Aug 7, 2019
0a3f472
Clarifies what to delete
krishnadurai Aug 7, 2019
e79609a
Rearranges and clarifies descriptions
krishnadurai Aug 7, 2019
c8f575b
Re-arranges and rephrases content
krishnadurai Aug 7, 2019
b9deeaf
Fixes link
krishnadurai Aug 7, 2019
6d84bbf
Addresses review comments
krishnadurai Aug 8, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 25 additions & 1 deletion content/docs/started/k8s/kfctl-k8s-istio.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,9 @@ This config creates a vanilla deployment of Kubeflow with all its core component

### Deploy Kubeflow

This Kubeflow deployment requires a default StorageClass with a [dynamic volume provisioner](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/). Verify the `provisioner` field of your default StorageClass definition.
If you don't have a provisioner, ensure that you have configured volume provisioning in your Kubernetes cluster appropriately as mentioned [below](#provisioning-of-persistent-volumes-in-kubernetes).

Follow these steps to deploy Kubeflow:

1. Download a `kfctl` release from the [Kubeflow releases page](https://github.com/kubeflow/kubeflow/releases/) and unpack it:
Expand All @@ -33,7 +36,7 @@ Follow these steps to deploy Kubeflow:
kfctl apply all -V
```

* **${KFAPP}** - the _name_ of a directory where you want Kubeflow
* **${KFAPP}** - the _name_ of a directory where you want Kubeflow
configurations to be stored. This directory is created when you run
`kfctl init`. If you want a custom deployment name, specify that name here.
The value of this variable becomes the name of your deployment.
Expand Down Expand Up @@ -86,6 +89,27 @@ Your Kubeflow app directory contains the following files and directories:
* **${KFAPP}/app.yaml** defines configurations related to your Kubeflow deployment.
* **${KFAPP}/kustomize**: contains the YAML manifests that will be deployed.

### Provisioning of Persistent Volumes in Kubernetes

Note that you can skip this step if you have a dynamic volume provisioner already installed in your cluster.

If you don't have one:

* You can choose to create PVs manually after deployment of Kubeflow.
* Or install a dynamic volume provisioner like [Local Path Provisioner](https://github.com/rancher/local-path-provisioner#deployment). Ensure that the StorageClass used by this provisioner is the default StorageClass.

### Troubleshooting
krishnadurai marked this conversation as resolved.
Show resolved Hide resolved

#### Persistent Volume Claims are in Pending State

Check if PersistentVolumeClaims get `Bound` to PersistentVolumes.
```
kubectl -n kubeflow get pvc

```

If the PersistentVolumeClaims (PVCs) are in `Pending` state after deployment and they are not bound to PersistentVolumes (PVs), you may have to either manually create PVs for each PVC in your Kubernetes Cluster or an alternative is to set up [dynamic volume provisioning](#provisioning-of-persistent-volumes-in-kubernetes) to create PVs on demand and redeploy Kubeflow after deleting existing PVCs.

### Next steps

* Run a [sample machine learning workflow](/docs/examples/resources/).
Expand Down