Skip to content

docs: add warning about multi-namespace Spark Operator deployments #4303

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.

Sign up for GitHub

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
Sanika123-art wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: add warning about multi-namespace Spark Operator deployments #4303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions ...ponents/spark-operator/user-guide/running-multiple-instances-of-the-operator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,20 @@ description: |
weight: 70
---

{{% alert title="Important" color="warning" %}}
Spark Operator creates **cluster-scoped resources** such as
`MutatingWebhookConfiguration`, `ValidatingWebhookConfiguration`, and `ClusterRole`.

Because of this, running Spark Operator instances in **different namespaces**
within the same Kubernetes cluster is **not supported** and will result in
resource conflicts.

The recommended approach is to:
- Deploy Spark Operator **once** (or multiple releases) in a **single operator namespace**
- Configure each instance to watch **different Spark job namespaces**
using `spark.jobNamespaces`
{{% /alert %}}

If you need to run multiple instances of the Spark operator within the same k8s cluster, then you need to ensure that the running instances should not watch the same spark job namespace.
For example, you can deploy two Spark operator instances in the `spark-operator` namespace, one with release name `spark-operator-1` which watches the `spark-1` namespace:

Expand Down