I create this parent ticket to track all the changes to graduate mxnet-operator to v1.
Configuration and deployment
| Description |
Category |
Status |
Issue |
| Kustomize package |
Required |
Done |
https://github.com/kubeflow/manifests/pull/279 |
| Application CR |
Required |
Not Done |
|
| Images listed in kustomization.yaml |
Required |
Not Done |
|
| Upgradeability |
Required |
Done |
|
| Separate cluster scoped and namespace scoped resources |
Recommended |
Done |
N/A |
| Kustomize package should be deployable on its own |
Recommended |
Not Done |
|
Custom Resources
| Description |
Category |
Status |
Issue |
| Version stability |
Required |
Not Done |
|
| Backward compatibility |
Required |
Not Done |
|
| Supports status subresource |
Required |
Not Done |
|
| CRD schema validation |
Required |
Not Done |
|
| Training operators follow kubeflow/common conventions |
Required |
Not Done |
|
Logging and monitoring
| Description |
Category |
Status |
Issue |
| Liveness/Readiness signals |
Required |
Not Done |
|
| Prometheus metrics |
Required |
Not Done |
|
| Json logging |
Recommended |
Not Done |
|
CI/CD
| Description |
Category |
Status |
Issue |
| E2E tests |
Required |
Not Done |
|
| Scalability / load testing |
Required |
Not Done |
|
| Continuous building of docker images |
Recommended |
Not Done |
|
| Continuous updating of Kustomize manifests |
Recommended |
Not Done |
|
Docs
| Description |
Category |
Status |
Issue |
| API Reference docs |
Required |
Not Done |
|
| Application docs |
Required |
Not Done |
|
Owners/Maintenance
| Description |
Category |
Explanation |
Status |
Issue |
| Healthy number of committers and commits |
Required |
Committers are listed as approvers in owners filesNumber to be determined by TOC based on size and scope of application |
Not Done |
|
| At least 2 different organizations are committers |
Required |
AWS, Caicloud, Huawei, Qihoo 360, TuSimple |
Done |
#63 |
Adoption
| Description |
Category |
Explanation |
| List of users running the application |
Recommended |
Suggest listing adopters willing to be identified publicly in ADOPTERS.md |
I start everything from Not Done, I will check every items and associate the issue/pr to the table
kubeflow
