Getting started guide for OpenShift #33
Comments
|
Websites are infinite. I'm sure we could find room to add some info. |
|
I've added this issue as a potential one to tackle during the upcoming Kubeflow Doc Sprint. Stay tuned for info about the doc sprint! |
|
/assign |
|
Hallo @pdmack How are you doing with this guide? (Have you earned a doc sprint T-shirt? ;) ) |
|
I am doing poorly due to other commitments. Still would like the XXL t-shirt though. |
|
You got it! I've just sent you your code by email. Claim the T-shirt by August 9th. |
|
If it helps, I'm doing some testing with OpenShift 4.2/CodeReady Containers: |
|
Hi, we have started working on creating I am happy to join and contribute it as part of the Doc Sprint:) |
|
/unassign @pdmack |
|
/area docs |
|
FYI we are mostly done with opendatahub-io/manifests#4 - there are still a few bits to be enabled and polished, but KFDef and manifests from that PR seem to mostly work for us |
|
Adding some info from a kubeflow-discuss thread: Work is currently in progress in a fork, which will be contributed to the Kubeflow repositories soon. To use Kubeflow on OpenShift, you should be able to use https://github.com/opendatahub-io/manifests/ with Kubeflow v0.7 and this kfdef file: https://github.com/opendatahub-io/manifests/blob/v0.7-branch-openshift/kfdef/kfctl_openshift.yaml It's been tested on OpenShift 4.2, and is expected to work on any OpenShift 4 version. It's not tested on OpenShift 3.x. Looking forward to seeing the docs emerge from the February doc sprint! :) |
|
More info from another kubeflow-discuss thread: If you want to deploy to OpenShift, make sure you have kfctl version 0.7, then clone the manifests (https://github.com/opendatahub-io/manifests) and run Assuming you are logged into an OpenShift cluster, you should see kubeflow namespace created with all the components deployed. |
|
@sarahmaddox With the above comment, I'd say we kind of finished our initial work for KF 0.7 on OpenShift. We will go over our changes and propose them also to KF master, but I wanted to ask - what would you think about adding a "how to install" section to kubeflow website pointing to our fork until the changes get back to the KF repositories? I am not sure what the policies for content of website are. |
|
@vpavlin Yes, it will be great if you add an installation section on kubeflow.org. It's fine for the installation page(s) to point to your fork until the changes are merged into the Kubeflow repositories. For Kubeflow users, it's good to have the installation guides in one place. Looking forward to seeing you at the doc sprint! |
|
@vpavlin I've moved this issue to In progress in the doc sprint Kanban board, because the issue is assigned to you. Happy sprinting! |
* Add LICENSE file * Delete LICENSE * Create LICENSE * Delete kserve_layer.png * Updated kserve_layer file * disable the animation * Add blog link * Added blog Section Added blog section Added articles sub-section Added KFserving transition blog * Moved blog to docs and added to mkdocs.yaml * Moved Images to images and fixed path * Fixed Image Path * changed image from html to markdown * Changed By **Dan Sun([email protected])** and **Animesh Singh([email protected])** on behalf of the Kubeflow Serving Working Group to Authors moved By **Dan Sun([email protected])** and **Animesh Singh([email protected])** on behalf of the Kubeflow Serving Working Group
Do we want/need a special getting started guide for open shift?
Related to kubeflow/kubeflow#240
/cc @willb @pdmack
The text was updated successfully, but these errors were encountered: