[GitHub] [zeppelin] Leemoonsoo commented on issue #3728: [ZEPPELIN-4748] Format Spark web ui url dynamically on Kubernetes

[GitBox <gi...@apache.org>]

Leemoonsoo commented on issue #3728: [ZEPPELIN-4748] Format Spark web ui url dynamically on Kubernetes
URL: https://github.com/apache/zeppelin/pull/3728#issuecomment-612091801
 
 
   Hi @Reamer. Thanks for the comment.
   
   Proxy sutff via nginx and go-dnsmasq is there to make Zeppelin on Kubernetes out of the box, including SparkUI, on minkube environment. The current configuration out of the Box does not include Ingress controller.
   
   So, it is up to the user to how to configure Ingress controller. One way (a) is like you did let each interpreter create Ingress configuration in their creation, another way (b) is to let one ingress controller accept all traffic and make nginx proxy route traffic to individual interpreters.
   
   I think it is better to let the user decide (a) or (b). while
     - some ingress controller (like cloud provider's ingress controller) takes few minutes to be created, and some does not (like nginx ingress controller)
     - some ingress controller takes additional cost (like cloud provider's ingress controller) on each creation, and some does not (like nginx ingress controller)
     - ingress controller need to be customized for each user (like host, path, domain name, subdomain name, tls, etc) 
   
   So, how about make out-of-box configuration ready for both (a) and (b), and let user decide which one to use?
   
   
   

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


With regards,
Apache Git Services