Custom resource
SparkApplication
Auto-generated derived type for SparkApplicationSpec via `CustomResource`
- API group
- spark.stackable.tech
- API versions in 26.3
- v1alpha1
- Scope
- Namespaced
- Operator
- Apache Spark
- Roles
- none
Schema
SparkApplication.spark.stackable.tech .spec fields for SDP 26.3.
Schema
- The actual application file that will be called by
spark-submit. - Mode: cluster or client. Currently only cluster is supported.allowed: clusterclient
- Specify which image to use, the easiest way is to only configure the
productVersion. You can also configure a custom image registry to pull from, as well as completely custom images. Consult the Product image selection documentation for details. - Arguments passed directly to the job artifact.
- Job dependencies: a list of python packages that will be installed via pip, a list of packages or repositories that is passed directly to spark-submit, or a list of excluded packages (also passed directly to spark-submit).
- The driver role specifies the configuration that, together with the driver pod template, is used by Spark to create driver pods.
- A list of environment variables that will be set in the job pod and the driver and executor pod templates.
- The executor role specifies the configuration that, together with the driver pod template, is used by Spark to create the executor pods. This is RoleGroup instead of plain CommonConfiguration because it needs to allow for the number of replicas. to be specified.
- The job builds a spark-submit command, complete with arguments and referenced dependencies such as templates, and passes it on to Spark. The reason this property uses its own type (SubmitConfigFragment) is because logging is not supported for spark-submit processes.
- The log file directory definition used by the Spark history server.
- The main class - i.e. entry point - for JVM artifacts.
- Configure an S3 connection that the SparkApplication has access to. Read more in the Spark S3 usage guide.
- A map of key/value strings that will be passed directly to spark-submit.
- Name of the Vector aggregator discovery ConfigMap. It must contain the key
ADDRESSwith the address of the Vector aggregator. Follow the logging tutorial to learn how to configure log aggregation with Vector. - A list of volumes that can be made available to the job, driver or executors via their volume mounts.