[ 
https://issues.apache.org/jira/browse/SUBMARINE-367?focusedWorklogId=380047&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-380047
 ]

ASF GitHub Bot logged work on SUBMARINE-367:
--------------------------------------------

                Author: ASF GitHub Bot
            Created on: 31/Jan/20 15:21
            Start Date: 31/Jan/20 15:21
    Worklog Time Spent: 10m 
      Work Description: asfgit commented on pull request #170: SUBMARINE-367. 
Support submarine configuration outside k8s
URL: https://github.com/apache/submarine/pull/170
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 380047)
    Time Spent: 20m  (was: 10m)

> Support submarine configuration outside k8s
> -------------------------------------------
>
>                 Key: SUBMARINE-367
>                 URL: https://issues.apache.org/jira/browse/SUBMARINE-367
>             Project: Apache Submarine
>          Issue Type: Sub-task
>          Components: Cloud-native Deployment
>            Reporter: Liu Xun
>            Assignee: Liu Xun
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.4.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We need to enable the submarine running in k8s to use an external 
> submarine-site.xml configuration file.
> In this way, the user can configure the submarine-site.xml file externally, 
> and then allow the submarine running in k8s to run according to the user's 
> settings.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to