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.

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

Extend Katib documentation to use not in GKE #2260

Merged
merged 7 commits into from Feb 5, 2019

Conversation

andreyvelich
Copy link
Member

@andreyvelich andreyvelich commented Jan 11, 2019

I added some information inside Katib package README.
How to deploy Katib not in GKE if you don't have StorageClass inside your cluster.


This change is Reviewable

@andreyvelich
Copy link
Member Author

@johnugeorge

@johnugeorge
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot removed the lgtm label Jan 14, 2019
@andreyvelich
Copy link
Member Author

@jlewi @YujiOshima
Please have a look on this PR.

@@ -16,27 +16,28 @@

## Quickstart

For running Katib you have to install tf-job operator and pytorch operator package.
For running Katib, you have to install tfjob operator and pytorch operator package.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe just say TF operator to be consistent with the repo name.

ks registry add kubeflow github.com/kubeflow/kubeflow/tree/master/kubeflow
```

### TF-job operator
### TFjob operator
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here - TF operator

@@ -55,6 +56,33 @@ ks generate katib katib
ks apply ${KF_ENV} -c katib
```

If you want to use Katib not in GKE and you don't have StorageClass for dynamic volume provisioning at your cluster, you have to create persistent volume to bound your persistent volume claim.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -65,5 +93,11 @@ ks delete ${KF_ENV} -c pytorch-operator
ks delete ${KF_ENV} -c tf-job-operator
```

If you create pv for Katib, delete it
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to delete the pvc as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@richardsliu Thank you for your review!
PVC will be deleted by this command
ks delete ${KF_ENV} -c katib.
Katib package includes PVC.

Add doc link for Persistent Volume
@jlewi
Copy link
Contributor

jlewi commented Feb 2, 2019

/assign @richardsliu

@richardsliu @johnugeorge Is the PR ready to merge? If so you can lgtm and approve it please?

@johnugeorge
Copy link
Member

/lgtm

@richardsliu
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardsliu

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit d95938f into kubeflow:master Feb 5, 2019
kkasravi pushed a commit to kkasravi/kubeflow that referenced this pull request Feb 8, 2019
* Add deploying Katib not in GKE in README

* Fix context

* Add context

* Move section for using Katib not in GKE

* Fix README

* Fix README

* Change name for TF operator
Add doc link for Persistent Volume
saffaalvi pushed a commit to StatCan/kubeflow that referenced this pull request Feb 11, 2021
* Add deploying Katib not in GKE in README

* Fix context

* Add context

* Move section for using Katib not in GKE

* Fix README

* Fix README

* Change name for TF operator
Add doc link for Persistent Volume
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants