[GitHub] [zeppelin] rickchengx commented on pull request #4174: [ZEPPELIN-5442] Allow users to set a separate namespace for the interpreter

[GitBox]

rickchengx commented on pull request #4174:
URL: https://github.com/apache/zeppelin/pull/4174#issuecomment-884048032


   
   > Thank you very much for your analysis. I understand the problems when 
Zeppelin server is running in K8s and they are not easy to solve.
   > Please add the documentation which explain the flag. Please make it clear 
that this feature only works when Zeppelin is running outside of K8s.
   
   Hi, @Reamer 
   Thanks for the comment. Due to potential code conflicts, I think it's better 
to achieve the feature of setting the separate namespace for the interpereter 
when Zeppelin server is running inside k8s. 
   
   So I added several commits to address the above three problems. Specifically,
   1. Change `role` and `rolebinding` to `clusterrole` and `clusterrolebinding`
   2. Update the conditions for setting `ownerReference`
   3. Return the correct namespace of Zeppelin Server
   
   
   Hence, it can set the separate namespace for each interpreter no matter 
Zeppelin server is running inside k8s or not.
   
   For example, user can start a spark interpreter in the namespace of `spark`:
   <img width="1403" alt="截屏2021-07-21 下午5 05 45" 
src="https://user-images.githubusercontent.com/38122586/126467521-975c35b0-d0fa-43c3-b7d9-7ef548752d6e.png";>
   <img width="866" alt="截屏2021-07-21 下午5 39 38" 
src="https://user-images.githubusercontent.com/38122586/126467929-6c7fc835-1e68-4d5a-ac95-f6483f5b4bb3.png";>
   
   Meanwhile, user can start a shell interpreter in the namespace of `sh`:
   <img width="1419" alt="截屏2021-07-21 下午5 02 55" 
src="https://user-images.githubusercontent.com/38122586/126468069-162d588a-f43a-4f01-9cd3-1d0aa35bdc37.png";>
   <img width="345" alt="截屏2021-07-21 下午5 03 04" 
src="https://user-images.githubusercontent.com/38122586/126468113-35c1214d-dfa4-4514-854a-6b5e888f63ec.png";>
   
   
   
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@zeppelin.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org