Installation
Alauda Build of Spark Operator is delivered as an OLM Operator and installed from the platform OperatorHub.
Prerequisites
- ACP version: v4.0 or later (validated on v4.3 / Kubernetes 1.34).
- Target cluster architecture
linux/amd64orlinux/arm64(the operator ships multi-arch images). - Operator Lifecycle Manager (OLM) available on the target cluster (provided by ACP).
Upload Operator
Download the Alauda Build of Spark Operator bundle from the Customer Portal / Marketplace (e.g. spark-operator.ALL.xxxx.tgz), then publish it to the platform repository with the violet command-line tool:
The operator bundle records its runtime images (the operator image and the Apache Spark runtime image) in the CSV relatedImages, so a violet release relocates them into the platform registry. This makes the operator installable on air-gapped clusters without reaching docker.io.
Install Operator
In the Administrator view:
- Click Marketplace / OperatorHub.
- At the top of the console, from the Cluster dropdown, select the destination cluster.
- Search for and select Alauda Build of Spark Operator, then click Install.
- Leave Channel unchanged (
stable). - Check that the Version matches the release you want to install (e.g.
v2.5.1). - Leave Installation Location unchanged — it defaults to the
spark-operatornamespace. - Choose an Upgrade Strategy (
Manualis recommended for production). - Click Install.
Verification
Confirm the Alauda Build of Spark Operator tile shows Installed, then verify on the cluster:
The operator watches all namespaces by default, so you can create SparkApplication resources in any namespace.
A Succeeded CSV means the operator controller is running. Spark workloads themselves only appear once you create a SparkApplication (or ScheduledSparkApplication) — see Run a Spark Application.