The Charm Store will undergo scheduled database maintenance on July 5, 2026 22:00 to July 6, 02:00 UTC. During this time, you may be unable to access charm and bundle metadata or publish updates. No user action is required and services will automatically resume once maintenance is complete.

Spark Integration Hub K8s

Canonical Publisher

Platform:

Channel Revision Published Runs on
latest/edge 132 10 Jun 2026
Ubuntu 22.04
3/stable 123 22 Apr 2026
Ubuntu 22.04
3/candidate 131 19 Jun 2026
Ubuntu 22.04
3/candidate 132 19 Jun 2026
Ubuntu 22.04
3/beta 133 25 Jun 2026
Ubuntu 22.04
3/beta 134 25 Jun 2026
Ubuntu 22.04
3/edge 134 25 Jun 2026
Ubuntu 22.04
3/edge 133 25 Jun 2026
Ubuntu 22.04
juju deploy spark-integration-hub-k8s --channel 3/stable

Learn about configurations >

  • driver-pod-template | string

    Define K8s driver pod from a file accessible to the spark-submit process. Ex.: "s3a://bucket/template.yml". Is equivalent to the following Spark configuration:

    spark.kubernetes.driver.podTemplateFile=<driver-pod-template>

  • enable-dynamic-allocation | boolean

    Enable dynamic allocation of pods for autoscaling Spark jobs. Is equivalent to the following Spark configurations:

    spark.dynamicAllocation.enabled=true spark.dynamicAllocation.shuffleTracking.enabled=true spark.dynamicAllocation.minExecutors=1

  • executor-pod-template | string

    Define K8s executor pods from a file accessible to the spark-submit process. Ex.: "s3a://bucket/template.yml". Is equivalent to the following Spark configuration:

    spark.kubernetes.executor.podTemplateFile=<executor-pod-template>

  • monitored-service-accounts | string

    Comma-separated patterns for namespaces and service accounts to monitor and update in addition to the ones managed by the charm's relations. Ex.: "namespace1:sa1,namespace2:*".

  • spark-image | string

    Define a custom Spark image to be used for driver and executor pods. If this option is set, the integration hub will supply the related application with an additional Spark property to use this image for drivers and executors. If not set, it's up to the related application to choose what image to use for the driver and executor pods.