[jira] [Resolved] (SUBMARINE-1230) Optimize submarine-operator-v3

["Kevin Su (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SUBMARINE-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Su resolved SUBMARINE-1230.
---------------------------------
    Fix Version/s: 0.9.0
       Resolution: Fixed

Issue resolved by pull request 1026
[https://github.com/apache/submarine/pull/1026]

> Optimize submarine-operator-v3
> ------------------------------
>
>                 Key: SUBMARINE-1230
>                 URL: https://issues.apache.org/jira/browse/SUBMARINE-1230
>             Project: Apache Submarine
>          Issue Type: Sub-task
>          Components: Cloud-native Deployment
>            Reporter: cdmikechen
>            Assignee: cdmikechen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.9.0
>
>
> * Add a config to replace image and other parameters related to image
> Currently, in the operator config, there is no property to change the image address of the init container image. 
> Using docker hub registry may cause the problem that the image cannot be pulled after exceeding the limit.
> * Move seldon-secret.yaml to operator
> Currently the secret in seldon-secret.yaml cannot be automatically created by operator based on submarine's CR creation.
> We need to make the operator capable of handling this secret as well.
> * Add env in server
> * Add pull secrets in CR
> * Log timestamp format
> * Dockfile additional parameters



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@submarine.apache.org
For additional commands, e-mail: dev-help@submarine.apache.org