Website: [DOCS] - "Outdated" files (69/250)

Created on 2 Sep 2020 · 24Comments · Source: kubeflow/website

Below is a list of all the outdated files on the docs today.

There are 120 files with "Out of date" out of the 250 files under /content/en/docs/:

./components/central-dash/overview.md
./components/central-dash/registration-flow.md
./components/fairing/configure-fairing.md
./components/fairing/fairing-overview.md
./components/fairing/gcp/configure-gcp.md
./components/fairing/gcp/tutorials/gcp-kubeflow-notebook.md
./components/fairing/gcp/tutorials/gcp-local-notebook.md
./components/fairing/install-fairing.md
./components/fairing/reference/sdk.md
./components/fairing/tutorials/other-tutorials.md
./components/feature-store/getting-started.md
./components/feature-store/overview.md
./components/jupyter.md
./components/misc/nuclio.md
./components/multi-tenancy/design.md
./components/multi-tenancy/getting-started.md
./components/multi-tenancy/overview.md
./components/serving/bentoml.md
./components/serving/tfbatchpredict.md
./components/serving/tfserving_new.md
./components/serving/tritoninferenceserver.md
./components/training/chainer.md
./components/training/mpi.md
./components/training/mxnet.md
./components/training/pytorch.md
./components/training/tftraining.md
./examples/blog-posts.md
./examples/codelabs-tutorials.md
./examples/kubeflow-samples.md
./examples/shared-resources.md
./examples/videos.md
./gke/anthos.md
./gke/cloud-filestore.md
./gke/custom-domain.md
./gke/customizing-gke.md
./gke/deploy/monitor-iap-setup.md
./gke/gcp-e2e.md
./gke/monitoring.md
./gke/pipelines/enable-gpu-and-tpu.md
./gke/pipelines/preemptible.md
./gke/private-clusters.md
./gke/troubleshooting-gke.md
./ibm/existing-cluster.md
./ibm/iks-e2e.md
./notebooks/custom-notebook.md
./notebooks/setup.md
./notebooks/submit-docker-image.md
./notebooks/submit-kubernetes.md
./notebooks/troubleshoot.md
./notebooks/why-use-jupyter-notebook.md
./openshift/install-kubeflow.md
./openshift/uninstall-kubeflow.md
./other-guides/freq-ask-questions.md
./other-guides/integrations/data-management.md
./other-guides/istio-in-kubeflow.md
./other-guides/job-scheduling.md
./other-guides/kubeflow-on-multinode-cluster.md
./other-guides/troubleshooting.md
./other-guides/usage-reporting.md
./pipelines/caching.md
./pipelines/overview/concepts/component.md
./pipelines/overview/concepts/experiment.md
./pipelines/overview/concepts/graph.md
./pipelines/overview/concepts/output-artifact.md
./pipelines/overview/concepts/pipeline.md
./pipelines/overview/concepts/run-trigger.md
./pipelines/overview/concepts/run.md
./pipelines/overview/concepts/step.md
./pipelines/overview/interfaces.md
./pipelines/overview/pipelines-overview.md
./pipelines/pipelines-quickstart.md
./pipelines/reference/component-spec.md
./pipelines/reference/sdk.md
./pipelines/sdk/best-practices.md
./pipelines/sdk/build-component.md
./pipelines/sdk/component-development.md
./pipelines/sdk/dsl-recursion.md
./pipelines/sdk/enviroment_variables.md
./pipelines/sdk/gcp.md
./pipelines/sdk/install-sdk.md
./pipelines/sdk/lightweight-python-components.md
./pipelines/sdk/manipulate-resources.md
./pipelines/sdk/output-viewer.md
./pipelines/sdk/parameters.md
./pipelines/sdk/pipelines-metrics.md
./pipelines/sdk/python-based-visualizations.md
./pipelines/sdk/sdk-overview.md
./pipelines/sdk/static-type-checking.md
./pipelines/troubleshooting.md
./pipelines/tutorials/api-pipelines.md
./pipelines/tutorials/build-pipeline.md
./pipelines/tutorials/cloud-tutorials.md
./pipelines/tutorials/sdk-examples.md
./reference/images.md
./reference/mpijob/v1alpha2/mpi.md
./reference/overview.md
./reference/pytorchjob/v1/pytorch.md
./reference/pytorchjob/v1beta2/pytorch.md
./reference/tfjob/v1/common.md
./reference/tfjob/v1/tensorflow.md
./reference/tfjob/v1beta2/common.md
./reference/tfjob/v1beta2/tensorflow.md
./reference/version-policy.md
./started/cloud/getting-started-aws.md
./started/cloud/getting-started-azure.md
./started/cloud/getting-started-gke.md
./started/getting-started.md
./started/k8s/kfctl-existing-arrikto.md
./started/k8s/kfctl-istio-dex.md
./started/k8s/kfctl-k8s-istio.md
./started/k8s/overview.md
./started/kubeflow-overview.md
./started/workstation/getting-started-linux.md
./started/workstation/getting-started-macos.md
./started/workstation/getting-started-minikf.md
./started/workstation/getting-started-multipass.md
./started/workstation/getting-started-windows.md
./started/workstation/minikf-gcp.md
./started/workstation/minikube-linux.md
./upgrading/upgrade.md

aredocs arejupyter areoperator arepipelines kinbug platforgcp prioritp1

Source

RFMVasconcelos

🚀2

Most helpful comment

I like the idea of regularly reviewing our docs, but I’m concerned that tagging each doc as outdated creates unnecessary toil for docs contributors. Are there any other docs projects that you know of that use this strategy? If so, what was their experience like?

WGs should be updating docs as a part of their work. This leads me to wonder, how much of the docset is expected to go stale with each release? If the WGs are updating their docs, then only a small portion of the docset should reasonably break in a release. Assuming that this is correct, the time spent checking docs may not feel worthwhile for contributors since they may test many pages without finding an issue. Testing a document like a tutorial is resource intensive. If contributors are asked to commit time to a task that does not seem sufficiently impactful, they may not participate or they may work around the system. (By writing a script to remove the tag.)

Perhaps we should address this issue in two ways. First, get each WG to review their docs once to verify that they currently have docs that work as expected. Second, going forward we could surface information to get reactive participation from the WGs. We could provide a report that links docs bugs to docs, so owners can respond to user feedback. We could also look at setting Kubeflow.org up to automatically add a “This page might be broken” link to docs with open issues. These links could open a GitHub issues query filtered to that doc’s issues.

That approach gives users insight into what may be broken, and ensures that WGs are aware of the issues that are reported for their docs. What do you think?

joeliedtke on 7 Oct 2020

👍4

All 24 comments

Issue-Label Bot is automatically applying the labels:

| Label | Probability |
| ------------- | ------------- |
| area/docs | 0.79 |
| kind/bug | 0.55 |

Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

issue-label-bot[bot] on 2 Sep 2020

@8bitmp3 @jlewi @Bobgy @joeliedtke @rmgogogo

I compiled this list of outdated docs. I did this 3 days ago, but only thought of pinging you now. Let me know how we can effectively tackle this issue 🚀

RFMVasconcelos on 5 Sep 2020

Thanks Rui. Would you share how to check it's "outdated" here? I may have less knowledge on it.

Do you mean compare it with the website and website doesn't have the latest content in Github?

rmgogogo on 9 Sep 2020

Thanks @RFMVasconcelos

Can we identify the owners for the relevant docs and file issues for them to update the docs? Maybe you can automate the opening of GitHub issues using the GitHub CLI/API?

For locations with outdated or no OWNERs files can we try to track down the appropriate owners or WG?

jlewi on 9 Sep 2020

@cspavlou @kimwnasptd @andreyvelich @james-jwu HI All, it appears that the docs are out of date for several components. Can we please try to get those updated by the end of October ?

jbottum on 4 Oct 2020

cc fyi @RFMVasconcelos @alfsuse @Jeffwan @neuromage @numerology @vpavlin @crobby @pdmack @shawnzhu @adrian555 @Tomcli

8bitmp3 on 6 Oct 2020

@jbottum @8bitmp3 @RFMVasconcelos thanks for driving this. If we want this to get fixed I think we need to

Create accountability
Create urgency

WGs and OWNERs files should solve the first problem.

Any ideas how we can create urgency? Do we need to establish of deleting docs older than X?

jlewi on 6 Oct 2020

@jbottum @8bitmp3 @RFMVasconcelos thanks for driving this. If we want this to get fixed I think we need to

Create accountability

Create urgency

WGs and OWNERs files should solve the first problem.

Any ideas how we can create urgency? Do we need to establish of deleting docs older than X?
How about open a PR and pin it at the top of the PR page with the disclaimer that if the author or anyone else will not update the docs before a certain date (end of October) the pages will be deleted?

how about update the list @RFMVasconcelos put together with the owner's name for each page? This way we will know who is working on what.

One important point I think we should pay attention to the sections root pages.. those shouldn't be deleted in any case

for the Workstation sections, I may work on the minikube pages and general ones.

alfsuse on 6 Oct 2020

Updated List - 106 out of 250 docs files are "Outdated"

Split by section:

Components: No general OWNERS file

./docs/components/jupyter.md

Central dash: No OWNERS file

./docs/components/central-dash/overview.md
./docs/components/central-dash/registration-flow.md

Fairing: No OWNERS file

./docs/components/fairing/configure-fairing.md
./docs/components/fairing/fairing-overview.md
./docs/components/fairing/gcp/configure-gcp.md
./docs/components/fairing/gcp/tutorials/gcp-kubeflow-notebook.md
./docs/components/fairing/gcp/tutorials/gcp-local-notebook.md
./docs/components/fairing/install-fairing.md
./docs/components/fairing/reference/sdk.md
./docs/components/fairing/tutorials/other-tutorials.md

Feature store: OWNERS

./docs/components/feature-store/getting-started.md
./docs/components/feature-store/overview.md

Misc: No OWNERS file

./docs/components/misc/nuclio.md

Multi-tenancy: No OWNERS file

./docs/components/multi-tenancy/design.md
./docs/components/multi-tenancy/overview.md

Serving: OWNERS

./docs/components/serving/bentoml.md
./docs/components/serving/tfbatchpredict.md
./docs/components/serving/tfserving_new.md
./docs/components/serving/tritoninferenceserver.md

Training: No OWNERS file

./docs/components/training/chainer.md
./docs/components/training/mpi.md
./docs/components/training/mxnet.md
./docs/components/training/pytorch.md
./docs/components/training/tftraining.md

Examples: No OWNERS file

./docs/examples/blog-posts.md
./docs/examples/codelabs-tutorials.md
./docs/examples/kubeflow-samples.md
./docs/examples/shared-resources.md
./docs/examples/videos.md

GKE: OWNERS

./docs/gke/anthos.md
./docs/gke/cloud-filestore.md
./docs/gke/custom-domain.md
./docs/gke/customizing-gke.md
./docs/gke/deploy/monitor-iap-setup.md
./docs/gke/gcp-e2e.md
./docs/gke/monitoring.md
./docs/gke/pipelines/enable-gpu-and-tpu.md
./docs/gke/pipelines/preemptible.md
./docs/gke/troubleshooting-gke.md

IBM: OWNERS

./docs/ibm/existing-cluster.md
./docs/ibm/iks-e2e.md

Notebooks: No OWNERS file

./docs/notebooks/custom-notebook.md
./docs/notebooks/setup.md
./docs/notebooks/submit-docker-image.md
./docs/notebooks/submit-kubernetes.md
./docs/notebooks/troubleshoot.md
./docs/notebooks/why-use-jupyter-notebook.md

Other guides: OWNERS

./docs/other-guides/freq-ask-questions.md
./docs/other-guides/integrations/data-management.md
./docs/other-guides/istio-in-kubeflow.md
./docs/other-guides/job-scheduling.md
./docs/other-guides/kubeflow-on-multinode-cluster.md
./docs/other-guides/troubleshooting.md
./docs/other-guides/usage-reporting.md

Pipelines: OWNERS

./docs/pipelines/caching.md
./docs/pipelines/overview/concepts/component.md
./docs/pipelines/overview/concepts/experiment.md
./docs/pipelines/overview/concepts/graph.md
./docs/pipelines/overview/concepts/output-artifact.md
./docs/pipelines/overview/concepts/pipeline.md
./docs/pipelines/overview/concepts/run-trigger.md
./docs/pipelines/overview/concepts/run.md
./docs/pipelines/overview/concepts/step.md
./docs/pipelines/overview/interfaces.md
./docs/pipelines/overview/pipelines-overview.md
./docs/pipelines/pipelines-quickstart.md
./docs/pipelines/reference/component-spec.md
./docs/pipelines/reference/sdk.md
./docs/pipelines/sdk/best-practices.md
./docs/pipelines/sdk/build-component.md
./docs/pipelines/sdk/component-development.md
./docs/pipelines/sdk/dsl-recursion.md
./docs/pipelines/sdk/enviroment_variables.md
./docs/pipelines/sdk/lightweight-python-components.md
./docs/pipelines/sdk/manipulate-resources.md
./docs/pipelines/sdk/output-viewer.md
./docs/pipelines/sdk/pipelines-metrics.md
./docs/pipelines/sdk/python-based-visualizations.md
./docs/pipelines/troubleshooting.md
./docs/pipelines/tutorials/api-pipelines.md
./docs/pipelines/tutorials/build-pipeline.md
./docs/pipelines/tutorials/cloud-tutorials.md
./docs/pipelines/tutorials/sdk-examples.md

Reference: OWNERS

./docs/reference/images.md
./docs/reference/mpijob/v1alpha2/mpi.md
./docs/reference/overview.md
./docs/reference/pytorchjob/v1/pytorch.md
./docs/reference/pytorchjob/v1beta2/pytorch.md
./docs/reference/tfjob/v1/common.md
./docs/reference/tfjob/v1/tensorflow.md
./docs/reference/tfjob/v1beta2/common.md
./docs/reference/tfjob/v1beta2/tensorflow.md

Getting started: OWNERS

./docs/started/cloud/getting-started-aws.md
./docs/started/cloud/getting-started-azure.md
./docs/started/cloud/getting-started-gke.md
./docs/started/getting-started.md
./docs/started/k8s/kfctl-existing-arrikto.md
./docs/started/k8s/overview.md
./docs/started/kubeflow-overview.md
./docs/started/workstation/getting-started-macos.md
./docs/started/workstation/getting-started-minikf.md
./docs/started/workstation/getting-started-windows.md
./docs/started/workstation/minikf-gcp.md
./docs/started/workstation/minikube-linux.md

Upgrading: No OWNERS file yet, PR

./docs/upgrading/upgrade.md

RFMVasconcelos on 6 Oct 2020

@jlewi @8bitmp3 @jbottum please find above the updated "outdated docs" list, by section of the website.

Accountability:

It seems that we're missing owners for Components (partial), Examples, and Notebooks.
Urgency:

As we struggle with limited capacity, I would suggest we specify priorities per OWNER. Maybe have OWNERS create an issue with their list of priorities and delivery predictions?

WDYT?

RFMVasconcelos on 6 Oct 2020

👍1

A relevant thread about the Upgrading section from https://github.com/kubeflow/website/pull/2257#issuecomment-703977899 by @jlewi

@8bitmp3 should we just delete these pages?
https://www.kubeflow.org/docs/upgrading/upgrade/

These docs no longer looks relevant.

@jlewi If you're OK with removing the whole section, we can do that (cc @RFMVasconcelos ). Then we together with OWNERS of each of the "subprojects" (AWS, IBM Cloud, Azure, Pipelines, etc) can start adding an upgrading-kubeflow.md to their directories. WDYT?

cc @Bobgy @joeliedtke

From OWNERS files:

Google Cloud docs/gke:
@Bobgy
@joeliedtke
@rmgogogo
IBM Cloud docs/ibm:
@adrian555
@animeshsingh
@shawnzhu
@Tomcli
Azure docs/azure:
@aronchick (we need to get that PR OKed - OWNERS for azure https://github.com/kubeflow/website/pull/2199) :)
AWS /docs/aws:
@Jeffwan
@PatrickXYS
Kubeflow Pipelines /docs/pipelines: should we have a separate upgrading KF section here?
@Bobgy
@IronPan
@neuromage
@Ark-kun
@numerology
@joeliedtke
@alfsuse
Getting started docs/started - add a paragraph or two with links?
@Bobgy
@knkski
Components - how do we proceed here?
components/feature-store
@woop
components/serving
@adrian555
@animeshsingh
@cliveseldon
@ellistarn
@ryandawsonuk
@Tomcli
@yuzisun

Other components...

8bitmp3 on 6 Oct 2020

👍2

That approach gives users insight into what may be broken, and ensures that WGs are aware of the issues that are reported for their docs. What do you think?

joeliedtke on 7 Oct 2020

👍4

Can somebody explain how docs that were written for Kubeflow 1.1 (feature store) are flagged as outdated? They shouldn't even be visible in 1.0 and yet that is what the pages now show.

woop on 7 Oct 2020

/reopen

PatrickXYS on 7 Oct 2020

@PatrickXYS: Reopened this issue.

In response to this:

/reopen

Instructions 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/test-infra repository.

k8s-ci-robot on 7 Oct 2020

Thank you so much for your awesome feedback @joeliedtke

Perhaps we should address this issue in two ways. First, get each WG to review their docs once to verify that they currently have docs that work as expected. Second, going forward we could surface information to get reactive participation from the WGs. We could provide a report that links docs bugs to docs, so owners can respond to user feedback. We could also look at setting Kubeflow.org up to automatically add a “This page might be broken” link to docs with open issues. These links could open a GitHub issues query filtered to that doc’s issues.

That approach gives users insight into what may be broken, and ensures that WGs are aware of the issues that are reported for their docs. What do you think?

💯% @joeliedtke 👍 👍 👍

What are your thoughts @PatrickXYS@adrian555 @animeshsingh @Tomcli @IronPan @numerology @neuromage @alfsuse @Jeffwan @aronchik @shawnzhu @rmgogogo @cliveseldon @knkski (and many more 😃 ) ?

Hi @woop! I think the docs were flagged as "outdated" during the v1.1 docs transition. Check out @jlewi and @RFMVasconcelos 's comments here: https://github.com/kubeflow/website/issues/1984#issuecomment-651421190 and https://github.com/kubeflow/website/issues/1984#issuecomment-661925946 I hope this helps!

8bitmp3 on 7 Oct 2020

👍1

First, get each WG to review their docs once to verify that they currently have docs that work as expected.
Second, going forward we could surface information to get reactive participation from the WGs.
I agree with @joeliedtke comment above but so I wonder do we have a WG for each section? I'm not aware of a WG for the "local/workstation" sections as an example.. should we create one?

I think we should put in place a process where each WG before any new release takes a review in advance so we know upfront which page needs to be re-worked and which not.

Also on another note:
Do we need a documentation lifecycle? Like, evaluate if a section/page is still useful over time and eventually remove it so as to maintain the overall documentation more "light".

alfsuse on 7 Oct 2020

👍1

Regarding adding a documentation lifecycle, that may be a good question to discuss in a community meeting. My initial thought is that we probably don't need full documentation reviews for minor releases. A full review may be more appropriate for a major release, since there is more potential for a breaking change.

joeliedtke on 7 Oct 2020

👍2

With current pace Kubeflow is evolving, a lot of docs become outdated even between minor releases. When looking at pipelines docs, there's really a lot I found, so I think it's a valuable process we can leverage

Bobgy on 9 Oct 2020

When looking at pipelines docs, there's really a lot I found

@Bobgy Any particular KFP ones that stood out and require an urgent refresh?

8bitmp3 on 9 Oct 2020

I'm collecting KFP doc updates and triage in https://github.com/kubeflow/pipelines/issues/4324

Bobgy on 12 Oct 2020

fyi Update to OWNERS

Azure docs/azure:
@aronchick

Both @eedorenko and @sudivate are also part of the Azure group 👍

cc @RFMVasconcelos

8bitmp3 on 14 Oct 2020

👍1

Update - 69 out of 250 files "outdated"

Hey everyone!

Following the last community meeting, here is an update on docs. We are making progress. From 120, we're now at 69 outdated pages. 🚀

We have also cleared the Getting Started and Overview pages, which, even if not perfect yet, do not appear "outdated" to new-comers anymore.

Tagging OWNERS of respective docs here so we can get that down to zero soon 🚀

cc @8bitmp3 @jbottum @jlewi @joeliedtke @Bobgy @alfsuse @woop @animeshsingh

Outdated pages

Getting started:

content/en/docs/started/workstation/getting-started-minikf.md
content/en/docs/started/workstation/minikf-gcp.md
content/en/docs/started/k8s/kfctl-existing-arrikto.md
content/en/docs/started/cloud/getting-started-aws.md
content/en/docs/started/cloud/getting-started-azure.md

@jbottum for arrikto/minikf docs
@Jeffwan @PatrickXYS for AWS
@aronchick @eedorenko @sudivate for Azure

Pipelines:

content/en/docs/pipelines/caching.md
content/en/docs/pipelines/troubleshooting.md
content/en/docs/pipelines/pipelines-quickstart.md
content/en/docs/pipelines/sdk/dsl-recursion.md
content/en/docs/pipelines/sdk/best-practices.md
content/en/docs/pipelines/sdk/output-viewer.md
content/en/docs/pipelines/sdk/component-development.md
content/en/docs/pipelines/sdk/pipelines-metrics.md
content/en/docs/pipelines/sdk/build-component.md
content/en/docs/pipelines/sdk/manipulate-resources.md
content/en/docs/pipelines/sdk/enviroment_variables.md
content/en/docs/pipelines/reference/component-spec.md
content/en/docs/pipelines/reference/sdk.md

OWNERS: @Bobgy @IronPan @neuromage @Ark-kun @numerology @joeliedtke @alfsuse

Components:

content/en/docs/components/misc/nuclio.md
content/en/docs/components/serving/tritoninferenceserver.md
content/en/docs/components/serving/bentoml.md
content/en/docs/components/serving/tfbatchpredict.md
content/en/docs/components/serving/tfserving_new.md
content/en/docs/components/multi-tenancy/design.md
content/en/docs/components/training/mpi.md
content/en/docs/components/training/pytorch.md
content/en/docs/components/training/chainer.md
content/en/docs/components/training/tftraining.md
content/en/docs/components/training/mxnet.md
content/en/docs/components/jupyter.md
content/en/docs/components/central-dash/overview.md
content/en/docs/components/central-dash/registration-flow.md
content/en/docs/components/feature-store/overview.md
content/en/docs/components/feature-store/getting-started.md
content/en/docs/components/fairing/install-fairing.md
content/en/docs/components/fairing/configure-fairing.md
content/en/docs/components/fairing/tutorials/other-tutorials.md
content/en/docs/components/fairing/fairing-overview.md
content/en/docs/components/fairing/reference/sdk.md

OWNERS:
@woop for components/feature-store
@adrian555 @animeshsingh @cliveseldon @ellistarn @ryandawsonuk @Tomcli @yuzisun for components/serving

WITH NO OWNERS file:

components/fairing
components/misc
components/multi-tenancy
components/central-dash

Is there anyone/SIG/WG who qualifies to lead these docs?

GKE:

content/en/docs/gke/gcp-e2e.md
content/en/docs/gke/customizing-gke.md
content/en/docs/gke/troubleshooting-gke.md
content/en/docs/gke/custom-domain.md
content/en/docs/gke/deploy/monitor-iap-setup.md
content/en/docs/gke/anthos.md
content/en/docs/gke/pipelines/enable-gpu-and-tpu.md
content/en/docs/gke/pipelines/preemptible.md
content/en/docs/gke/cloud-filestore.md
content/en/docs/gke/monitoring.md

OWNERS: @Bobgy @joeliedtke @rmgogogo

Other guides:

content/en/docs/other-guides/kubeflow-on-multinode-cluster.md
content/en/docs/other-guides/freq-ask-questions.md
content/en/docs/other-guides/troubleshooting.md
content/en/docs/other-guides/istio-in-kubeflow.md
content/en/docs/other-guides/integrations/data-management.md
content/en/docs/other-guides/usage-reporting.md
content/en/docs/other-guides/job-scheduling.md

OWNERS: @8bitmp3 @RFMVasconcelos

Notebooks:

content/en/docs/notebooks/custom-notebook.md
content/en/docs/notebooks/troubleshoot.md
content/en/docs/notebooks/setup.md
content/en/docs/notebooks/submit-docker-image.md
content/en/docs/notebooks/submit-kubernetes.md
content/en/docs/notebooks/why-use-jupyter-notebook.md

No OWNERS file, should be created.
Notebooks WG OWNERS: @thesuperzapper @StefanoFioravanzo @elikatsis @kimwnasptd

Reference:

content/en/docs/reference/mpijob/v1alpha2/mpi.md
content/en/docs/reference/pytorchjob/v1/pytorch.md
content/en/docs/reference/pytorchjob/v1beta2/pytorch.md
content/en/docs/reference/tfjob/v1/common.md
content/en/docs/reference/tfjob/v1/tensorflow.md
content/en/docs/reference/tfjob/v1beta2/common.md
content/en/docs/reference/tfjob/v1beta2/tensorflow.md

OWNERS: @andreyvelich @gaocegege @Jeffwan @johnugeorge @terrytangyuan

RFMVasconcelos on 22 Oct 2020

🎉2 👍1

Hi @RFMVasconcelos, thank you for driving this.
I've added OWNERS for multi-tenancy. https://github.com/kubeflow/website/blob/master/content/en/docs/components/multi-tenancy/OWNERS

Bobgy on 23 Oct 2020

👍2

Was this page helpful?

0 / 5 - 0 ratings