Skip to content
This repository has been archived by the owner on Sep 19, 2022. It is now read-only.

PyTorch Operator: Move manifests development upstream #320

Conversation

yanniszark
Copy link
Contributor

Issue Resolved

Resolves: #318
Umbrella issue: kubeflow/manifests#1740

Description

As part of the work of wg-manifests for 1.3
(kubeflow/manifests#1735), we are moving manifests
development in upstream repos. This gives the application developers full
ownership of their manifests, tracked in a single place.

This PR copies the manifests for application PyTorch Operator
from path apps/pytorch-job/upstream of kubeflow/manifests to path
manifests of the upstream repo (https://github.com/kubeflow/pytorch-operator).

cc @kubeflow/wg-training-leads

As part of the work of wg-manifests for 1.3
(kubeflow/manifests#1735), we are moving manifests
development in upstream repos. This gives the application developers full
ownership of their manifests, tracked in a single place.

This commit copies the manifests for application `PyTorch Operator`
from path `apps/pytorch-job/upstream` of kubeflow/manifests to path
`manifests` of the upstream repo (https://github.com/kubeflow/pytorch-operator).

Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
@coveralls
Copy link

Coverage Status

Coverage remained the same at 64.11% when pulling 6c21fec on arrikto:feature-move-pytorch-operator-manifests-upstream into 6293efc on kubeflow:master.

Copy link
Member

@terrytangyuan terrytangyuan left a comment

Choose a reason for hiding this comment

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

/lgtm

@yanniszark
Copy link
Contributor Author

@terrytangyuan is there any work remaining for merging the PR?

@terrytangyuan
Copy link
Member

I'd defer to @johnugeorge and others from @kubeflow/wg-training-leads to confirm since I didn't author these manifests originally.

Copy link
Member

@andreyvelich andreyvelich left a comment

Choose a reason for hiding this comment

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

Thank you @yanniszark.
Should we also delete the current manifests and update the CI/CD ?

metadata:
labels:
name: pytorch-operator
annotations:
Copy link
Member

Choose a reason for hiding this comment

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

Why do we disable istio for the PyTorchJob controller ?

@@ -0,0 +1,3 @@
pytorchDefaultImage=null
Copy link
Member

Choose a reason for hiding this comment

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

I think we can remove this file

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jeffwan, terrytangyuan, yanniszark

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 476308f into kubeflow:master Feb 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PyTorch Operator: Move manifests development upstream
6 participants