maziyarpanahi opened a new pull request, #4439: URL: https://github.com/apache/zeppelin/pull/4439
- There has never been any Docker image named `zeppelin-interpreter` or `zeppelin-server`. - The latest version also should be 0.10.1 ### What is this PR for? A few sentences describing the overall goals of the pull request's commits. First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html All the examples inside and outside Zeppelin website/docs point to simply using `zeppelin-server.yaml` for K8s cluster 👍🏼 ``` curl -s -O https://raw.githubusercontent.com/apache/zeppelin/master/k8s/zeppelin-server.yaml ``` There are lots of issues on StackOverFlow and 1 on Jira that indicate the Docker images mentioned in this YAML simply don't exist on Docker Hub. ### What type of PR is it? Documentation *Please leave your type of PR only* ### Todos * [ ] - Task ### What is the Jira issue? * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/ * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. [ZEPPELIN-533] https://issues.apache.org/jira/browse/ZEPPELIN-5191 ### How should this be tested? * Strongly recommended: add automated unit tests for any new or changed behavior * Outline any manual steps to test the PR here. I have tested this on a live K8s cluster (OpenStack) and it created a Zeppelin server successfully, also creates Spark and other interpreters in the cluster upon request without any issue: ``` curl -s -O https://raw.githubusercontent.com/apache/zeppelin/master/k8s/zeppelin-server.yaml ``` ### Screenshots (if appropriate) ### Questions: * Does the licenses files need to update? * Is there breaking changes for older versions? * Does this needs documentation? -- 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
