helm-media-servarr

Bazarr Helm Chart

This Helm chart installs Bazarr, a companion application for Radarr and Sonarr to manage and download subtitles

This README covers the basics of customising and installation

• Installation
• Configuration
  • Secrets
  • Application Configuration
  • Volumes
  • Ingress
  • Metrics
  • Advanced
• Upgrading
• Uninstallation
• Support

Installation

Install this helm chart using the following command:

helm repo add media-servarr https://media-servarr.shw.al/charts

helm install bazarr media-servarr/bazarr

Pointing the host media-servarr.local to your kubernetes cluster will then allow you to access the application at the default location of http://media-servarr.local/bazarr/

Configuration

Here are some examples of configuration you may want to override (and include in installation with -f myvalues.yaml).

Secrets

To set up secrets, like API keys, use the following format.

Use openssl rand -hex 16 to generate a key and replace the default value. If using a ConfigMap to manage configuration, you can also set various other secrets here too - such as service passwords, or sonarr and radarr API keys.

secrets:
  # inline value
  - name: 'apiKey'
    value: 'your-api-key-here'

  # reference pre-existing Secret
  - name: 'sonarrApiKey'
    ref: 'sonarr-api-key'
  - name: 'radarrApiKey'
    ref: 'radarr-api-key'

When ref is set, the chart reads key name from the Secret named by ref in the same namespace.

By not setting this value, and leaving it blank, Bazarr will automatically generate a new key on start.

Application Configuration

By default, base configuration is defined using a ConfigMap - defined by default in ./values.yaml in application.config. You can change values in the contents, such as the url base in your custom values.yaml.

The list of configurable items is extensive. You can configure service providers directly here, for example. Only a selection of core settings are included in the existing ConfigMap in values.yaml - But an exhaustive list is included in config.example.yaml

The following example expects to have secrets set up for Radarr and Sonarr API keys for secret injection:

application:
  port: 6767 # default UI port
  urlBase: 'bazarr' # default web base path
  config:
    contents: |
      general:
        adaptive_searching: true
        auto_update: false
        base_url: '/bazarr'
        port: 6767
        use_radarr: false
        use_sonarr: false
        radarr:
          apiKey: '$radarrApiKey'
          base_url: '/radarr'
          ip: 'radarr.media-servarr.svc.cluster.local'
          port: 7878
        sonarr:
          apiKey: '$sonarrApiKey'
          base_url: '/sonarr'
          ip: 'sonarr.media-servarr.svc.cluster.local'
          port: 8989
    # Secrets to inject the config they must be defined as $secret
    secrets:
      - 'apiKey'
      - 'sonarrApiKey'
      - 'radarrApiKey'

You can prevent a ConfigMap being created and the configuration being managed as a kubernetes resource by defining the config as null. For example:

application:
  ...
  config: null

Volumes

A volume is included just for configuration:

• config - General config data, where the sqlite database exists, for example

deployment:
  ...
  volumes:
    config: # The key will be the volume name
      persistentVolumeClaim:
        claimName: 'bazarr-config'

By default, a PersistentVolumeClaim will be provisioned for the config named bazarr-config.

persistentVolumeClaims:
  bazarr-config:
    accessMode: 'ReadWriteOnce'
    requestStorage: '1Gi'
    storageClassName: 'manual'
    # volumeName: 'existing-pv-name'  # optional: bind this PVC to a specific pre-existing PV
    selector:
      matchLabels:
        type: 'local'

Ingress

Ingress can be enabled, and you can customise the default host, path, and TLS settings:

ingress:
  enabled: true
  host: 'example.com'
  tls:
    # Your TLS settings...

Metrics

Enabling metrics enables a sidecar container being attached for exportarr - and a ServiceMonitor CRD to be consumed by the kube-prometheus package.

By default, Exportarr reads the apiKey from this chart’s Secret. If you need Exportarr to read a different Secret/key, set metrics.apiref.

metrics:
  enabled: true
  apiref:
    secret: 'my-existing-secret'
    keyname: 'apiKey'
  env: []

It is recommended to install kube-prometheus chart first for the CRD to be supported. It is not included as a dependency by default in this package!

Unless changed with metrics.port.number you can then consume metrics over port 9700.

Advanced

Other supported deployment configuration include deployment.nodeSelector, deployment.tolerations, and deployment.affinity

You can also adjust container ports, environment variables (such as adding PGID and PUID) and define a serviceAccount.

Have a look at the parent charts default values.yaml for a comprehensive list of available config.

Upgrading

To upgrade the deployment:

helm upgrade bazarr media-servarr/bazarr -f myvalues.yaml

Uninstallation

To uninstall/delete the bazarr deployment:

helm uninstall bazarr

Support

For support, issues, or feature requests, please file an issue on the chart’s repository issue tracker.

This site is open source. Improve this page.