You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Currently, mxnet operator API doesn't follow
kubeflow/common
convention and but controller does. It imports tf-operator implementationhttps://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 forActiveDeadlineSeconds
,BackoffLimit
, etc. This will simplifies the implementation on mxnet-operator side.The text was updated successfully, but these errors were encountered: