Skip to content
This repository was archived by the owner on Feb 1, 2022. It is now read-only.

Change to follow kubeflow/common convention and reuse implementation #72

@Jeffwan

Description

@Jeffwan

Currently, mxnet operator API doesn't follow kubeflow/common convention and but controller does. It imports tf-operator implementation https://github.com/kubeflow/mxnet-operator/blob/c718707b304dc1ed0210a740c8efe7071d4ebb3e/pkg/controller.v1/mxnet/controller.go#L42

To graduate mxnet-operator to v1, we'd like to migrate to follow kubecom/common convention. It already has all the logic for ActiveDeadlineSeconds, BackoffLimit, etc. This will simplifies the implementation on mxnet-operator side.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions