Reamer commented on issue #3728: [ZEPPELIN-4748] Format Spark web ui url dynamically on Kubernetes URL: https://github.com/apache/zeppelin/pull/3728#issuecomment-612383791 > So, how about make out-of-box configuration ready for both (a) and (b), and let user decide which one to use? I totally agree with you. Thanks for your explanations. I host K8s on my own hardware, so I wasn't aware of the additional costs and time in public clouds. You misunderstood me a bit about how I want to use k8s deployments. The interpreter should run in a pod, only the Zeppelin server should be controlled by a deployment. When the Zeppelin server pod dies, the deployment controller creates a new Zeppelin server pod. Child k8 resources created by the old pod should be deleted, including interpreter pods, roles, role binding, services, etc. I think it is quite complicated to recreate a stateful Interpreter pod with a K8s-deployment, because it's internally controlled by K8s and the Zeppelin server doesn't know about it. To simplify this, we should trigger the creation of a new pod from the Zeppelin server. It is possible that we change the out-of-box configuration (b) to a Zeppelin server deployment? I will add version (a), if I have time. Best Regards Reamer
---------------------------------------------------------------- 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] With regards, Apache Git Services
