Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Resolved
-
None
-
None
Description
The old submarine-operator is very old, and it is incompatible with the current Submarine version. Now, the operator has the following problems.
(1) (submarine-operator.md) Kind v0.6.0 deprecates kind get kubeconfig-path
(2) (manifests/submarine-operator/deployment.yaml) selector field is necessary.
(3) (manifests/submarine-operator/deployment.yaml) Now, deployment is apiVersion: apps/v1 rather than extensions/v1beta1.
(4) The .yaml files in manifests/ are very different with the files in helm-charts/. Therefore, some errors will occur. For instance, there is no configMap in helm-charts/submarine/templates/submarine-server.yaml, but a configMap is defined in manifests/submarine-cluster/submarine-server.yaml.
(5) It is hard to know the existing functionalities of this operator.
(6) Some parts need to generate by code-generator, and these parts should not be modified manually. (Link)
Attachments
Issue Links
- is a parent of
-
SUBMARINE-768 Use code-generator to generate API
- Resolved
-
SUBMARINE-770 Create Submarine CRD & Test API generated by code-generator
- Resolved
-
SUBMARINE-771 Implement Controller Pattern
- Resolved
-
SUBMARINE-776 Operator Testing framework
- Resolved
-
SUBMARINE-783 Run submarine-operator in k8s cluster
- Resolved
-
SUBMARINE-786 Use helm in k8s cluster
- Resolved
-
SUBMARINE-791 Read Submarine CRD spec in controller
- Resolved
-
SUBMARINE-797 Create a Submarine service for a single user
- Resolved
-
SUBMARINE-816 Implement Submarine delete event handler
- Resolved
-
SUBMARINE-900 Create a submarine mlflow for single user
- Resolved
-
SUBMARINE-904 Create minio by submarine operator for single user
- Resolved
- relates to
-
SUBMARINE-894 Reduce the image size of submarine-operator
- Resolved