-
Notifications
You must be signed in to change notification settings - Fork 6
Add documentation for Zeppelin with Spark on Kubernetes #21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
echarles
wants to merge
9
commits into
apache-spark-on-k8s:master
Choose a base branch
from
datalayer-externals:zeppelin
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
da41245
Add documentation for Zeppelin with Spark on Kubernetes
echarles 32804a5
fix typo
echarles 30926f1
zeppelin images with white background
echarles 6b1369d
fix typos further to @felixcheung comments
echarles ab72eb8
update doc, mainly on spark.app.name, to deal with latest commit on t…
echarles 7cc3432
fix typo and link to zeppelin chart to test - thx @felixcheung
echarles 833f6a9
Merge branch 'master' into zeppelin
echarles 1e4eeab
mark zeppelin doc as experimental + better document spark.app.name
echarles 0b661b0
fix link text
echarles File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,76 @@ | ||
--- | ||
layout: global | ||
displayTitle: Apache Zeppelin running with Spark on Kubernetes | ||
title: Apache Zeppelin running with Spark on Kubernetes | ||
description: User Documentation for Apache Zeppelin running with Spark on Kubernetes | ||
tag: experimental | ||
--- | ||
|
||
**Apache Zeppelin with Spark on Kubernetes is `experimental`** | ||
|
||
> At the time being, the needed code is not integrated in the `master` branches of `apache-zeppelin` nor the `apache-spark-on-k8s/spark` repositories. | ||
> You are welcome to already ty it out and send any feedback and question. | ||
|
||
First things first, you have to choose the following modes in which you will run Zeppelin with Spark on Kubernetes: | ||
|
||
+ The `Kubernetes modes`: Can be `in-cluster` (within a Pod) or `out-cluster` (from outside the Kubernetes cluster). | ||
+ The `Spark deployment modes`: Can be `client` or `cluster`. | ||
|
||
Only three combinations of these options are supported: | ||
|
||
1. `in-cluster` with `spark-client` mode. | ||
2. `in-cluster` with `spark-cluster` mode. | ||
3. `out-cluster` with `spark-cluster` mode. | ||
|
||
For now, to be able to test these combinations, you need to build specific branches (see hereafter) or to use third-party Helm charts or Docker images. The needed branches and related PR are listed here: | ||
|
||
1. In-cluster client mode [see pull request #456](https://github.com/apache-spark-on-k8s/spark/pull/456) | ||
2. Add support to run Spark interpreter on a Kubernetes cluster [see pull request #2637](https://github.com/apache/zeppelin/pull/2637) | ||
|
||
## In-Cluster with Spark-Client | ||
|
||
 | ||
|
||
Build a new Zeppelin based on [#456 In-cluster client mode](https://github.com/apache-spark-on-k8s/spark/pull/456). | ||
|
||
Once done, deploy that new build in a Kubernetes Pod with the following interpreter settings: | ||
|
||
+ `spark.master`: k8s://https://kubernetes:443 | ||
+ `spark.submit.deployMode`: client | ||
+ `spark.kubernetes.driver.pod.name`: The name of the pod where your Zeppelin instance is running. | ||
+ `spark.app.name`: Any name you want, without space nor special characters. | ||
+ Other spark.k8s properties you need to make your spark working (see [Running Spark on Kubernetes](./running-on-kubernetes.html)) such as `spark.kubernetes.initcontainer.docker.image`, `spark.kubernetes.driver.docker.image`, `spark.kubernetes.executor.docker.image`... | ||
|
||
## In-Cluster with Spark-Cluster | ||
|
||
 | ||
|
||
Build a new Zeppelin Docker image based on [#2637 Spark interpreter on a Kubernetes](https://github.com/apache/zeppelin/pull/2637). | ||
|
||
Once done, deploy that new build in a Kubernetes Pod with the following interpreter settings: | ||
|
||
+ `spark.master`: k8s://https://kubernetes:443 | ||
+ `spark.submit.deployMode`: cluster | ||
+ `spark.kubernetes.driver.pod.name`: Do not set this property. | ||
+ `spark.app.name`: Any name you want, without space nor special characters. | ||
+ Other spark.k8s properties you need to make your spark working (see [Running Spark on Kubernetes](./running-on-kubernetes.html)) such as `spark.kubernetes.initcontainer.docker.image`, `spark.kubernetes.driver.docker.image`, `spark.kubernetes.executor.docker.image`... | ||
|
||
## Out-Cluster with Spark-Cluster | ||
|
||
 | ||
|
||
Build a new Spark and their associated docker images based on [#2637 Spark interpreter on a Kubernetes](https://github.com/apache/zeppelin/pull/2637). | ||
|
||
Once done, any vanilla Apache Zeppelin deployed in a Kubernetes Pod (your can use a Helm chart for this) will work out-of-the box with the following interpreter settings: | ||
|
||
+ `spark.master`: k8s://https://ip-address-of-the-kube-api:6443 (port may depend on your setup) | ||
+ `spark.submit.deployMode`: cluster | ||
+ `spark.kubernetes.driver.pod.name`: Do not set this property. | ||
+ `spark.app.name`: Any name you want, without space nor special characters. | ||
+ Other spark.k8s properties you need to make your spark working (see [Running Spark on Kubernetes](./running-on-kubernetes.html)) such as `spark.kubernetes.initcontainer.docker.image`, `spark.kubernetes.driver.docker.image`, `spark.kubernetes.executor.docker.image`... | ||
|
||
## How to test | ||
|
||
For now, you will have to build custom Spark or Zeppelin Docker images to suit your needs. | ||
|
||
[Helm Charts for Zeppelin](https://github.com/kubernetes/charts/blob/master/stable/spark/templates/spark-zeppelin-deployment.yaml) are available to deploy on your Kubernetes cluster. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed in the meeting today, we want to ensure that these branches merge before we can publish documentation.
cc @felixcheung @erikerlandson @liyinan926 @mccheah