docs: add warning about multi-namespace Spark Operator deployments#4303
docs: add warning about multi-namespace Spark Operator deployments#4303Sanika123-art wants to merge 1 commit intokubeflow:masterfrom
Conversation
|
Hi @Sanika123-art. Thanks for your PR. I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
🚫 This command cannot be processed. Only organization members or owners can use the commands. |
Signed-off-by: sanika palav <palavsanika62@gmail>
97eabc9 to
a886077
Compare
What this PR does
Adds an Important alert to the Spark Operator documentation explaining that
the operator creates cluster-scoped resources (such as webhooks and ClusterRoles),
which makes running instances in different namespaces within the same cluster
unsupported.
Why this change is needed
Users attempting to deploy multiple Spark Operator instances may encounter
resource conflicts that are not clearly documented today. This change makes the
limitation explicit and guides users toward the recommended approach of using a
single operator namespace with different Spark job namespaces.
Related issue