You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by GitBox <gi...@apache.org> on 2020/04/29 11:20:21 UTC

[GitHub] [zeppelin] Reamer opened a new pull request #3753: [ZEPPELIN-4782] Correct K8s service usage in Zeppelin server

Reamer opened a new pull request #3753:
URL: https://github.com/apache/zeppelin/pull/3753


   ### What is this PR for?
   With this PR, we render the K8s-Service name into the Zeppelin interpreter start command for the initial connection.
   The K8s-Service name should be variable, because the name can differ between environments. 
   
   ### What type of PR is it?
    - Bug Fix
   
   ### Todos
   * [ ] - Task
   
   ### What is the Jira issue?
   * https://issues.apache.org/jira/browse/ZEPPELIN-4782
   
   ### How should this be tested?
   * Travis-CI: https://travis-ci.org/github/Reamer/zeppelin/builds/680915013
   
   ### Screenshots (if appropriate)
   
   ### Questions:
   * Does the licenses files need update? No
   * Is there breaking changes for older versions? No
   * Does this needs documentation? No
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [zeppelin] Leemoonsoo commented on pull request #3753: [ZEPPELIN-4782] Correct K8s service usage in Zeppelin server

Posted by GitBox <gi...@apache.org>.
Leemoonsoo commented on pull request #3753:
URL: https://github.com/apache/zeppelin/pull/3753#issuecomment-621502768


   LGTM. Merge to master and branch-0.9 if no further comment.


----------------------------------------------------------------
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:
users@infra.apache.org