rickchengx commented on pull request #4174: URL: https://github.com/apache/zeppelin/pull/4174#issuecomment-880387057
> Feature should also be available for Zeppelin server running in K8s + CI failures. Hi, @Reamer Thanks for your comment. I have fixed the CI failure. After my test, when zeppelin server is also running inside k8s, there'll be a few more problems: 1. the zeppelin server needs to obtain the **cluster role** instead of role to create pods and services in other namespaces. 2. There're 2 namespaces: the namespace of zeppelin server and the namespace of zeppelin interpreter. So the namespace return by method `getNamespace` may be wrong if we return the `zeppelin.k8s.interpreter.namespace` while zeppelin server is also running in k8s. 3. When zeppelin server pod and interpreter pod are in different namespaces, the `ownerReference` can not be set. Since Cross-namespace owner references are disallowed by design <https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/>. But if zeppelin server is running outside k8s, it can correctly create the interpreter pod in different namespaces. There won't be a problem of cross-namespace communication between zeppelin server and interpreter. So how about support the feature of separate namespace while zeppelin server is running in k8s in another PR. -- 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
