Reamer commented on issue #3728: [ZEPPELIN-4748] Format Spark web ui url dynamically on Kubernetes URL: https://github.com/apache/zeppelin/pull/3728#issuecomment-611928956 Hi @Leemoonsoo, Can we completely remove the proxy stuff via nginx and go-dnsmasq in the Zeppelin pod and use k8s resources? I tried to workaround some things with the goal of a cleaner k8s deployment. At the moment I use this [interpreter-spec.](https://gist.github.com/Reamer/c4d777ab76aae1bbbf1c64fea59a8a45) This creates an ingress and a service resource for every interpreter pod. Because of that, I doesn't need the nginx-proxy and dnymasq. I disabled sparkUI completely, because the URL in zeppelin-server GUI is wrong, but I can access the sparkUI manually via ingress. I use a [K8s-Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) to manage the zeppelin server. The current [pod example](https://github.com/apache/zeppelin/blob/master/k8s/zeppelin-server.yaml#L77-L166) is unsatisfactory, because if a [Node dies](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-lifetime) the pod also dies. My zeppelin-server deployment looks like this. [GitHub-Gist](https://gist.github.com/Reamer/bac4e568064809160c969034ed5a4b18). Because of the deployment, this [condition in zeppelin code](https://github.com/apache/zeppelin/blob/98b26a12f4ebe73e9ab9aa011e9a8a56731addbe/zeppelin-plugins/launcher/k8s-standard/src/main/java/org/apache/zeppelin/interpreter/launcher/K8sStandardInterpreterLauncher.java#L112) isn't truth any more. Therefore I'm using [a small workaround](https://gist.github.com/Reamer/c4d777ab76aae1bbbf1c64fea59a8a45#file-interpreter-spec-yml-L51). We should be able to render a correct webUI for the zeppelin GUI, because the zeppelin-server itself creates the pod, service and ingress object, I hope that are not to much changes and you can follow my idea. What you're thinking about that?
---------------------------------------------------------------- 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
