[
https://issues.apache.org/jira/browse/SUBMARINE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
cdmikechen resolved SUBMARINE-760.
----------------------------------
Resolution: Resolved
We have fixed most of the issues in 0.7.0, the remaining issues will be moved
to v3
> Refactor submarine-operator
> ---------------------------
>
> Key: SUBMARINE-760
> URL: https://issues.apache.org/jira/browse/SUBMARINE-760
> Project: Apache Submarine
> Issue Type: Improvement
> Components: Cloud-native Deployment
> Reporter: Kai-Hsun Chen
> Assignee: Kai-Hsun Chen
> Priority: Major
> Fix For: 0.8.0
>
>
> 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|https://github.com/kubernetes/sample-controller])
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org
For additional commands, e-mail: dev-h...@submarine.apache.org
