helm-media-servarr

tinyMediaManager Helm Chart

This Helm chart installs tinyMediaManager, a media manager for movies and TV shows, in a Kubernetes cluster.

This README covers the basics of customising and installation

• Installation
• Configuration
  • Application Configuration
  • Volumes
  • Ingress
  • 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 tinymediamanager media-servarr/tinymediamanager

By default, this chart exposes tinyMediaManager at http://tinymediamanager.local/

Configuration

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

Application Configuration

A startup configuration is defined using a ConfigMap in application.config

application:
  port: 4000
  config:
    filename: 'launcher-extra.yml'
    contents: |
      jvmOpts:
        - "-Xmx1024m"
    mountPath: '/app/launcher-extra.yml'

The chart exposes two container ports: http (4000, the web UI) and api (7878, the REST API used by companion apps). Both are declared in deployment.container.ports and exposed on the Service.

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

Three volumes are available by default:

• data - tinyMediaManager application data, logs, cache, and backups
• film - Location of movies
• television - Location of TV shows

deployment:
  ...
  volumes:
    data:
      persistentVolumeClaim:
        claimName: 'tinymediamanager-data'
    film:
      nfs:
        server: 'fileserver.local'
        path: '/srv/media/film/'
    television:
      nfs:
        server: 'fileserver.local'
        path: '/srv/media/television/'

By default, a PersistentVolumeClaim will be provisioned for data, but emptyDir: {} will be used for film and television unless otherwise specified in your values.yaml

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

Ingress

tinyMediaManager is best exposed on a dedicated host at /, rather than under a shared path prefix. This chart therefore defaults to a dedicated host and a root path.

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

Advanced

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

You can also adjust container ports, environment variables 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 tinymediamanager media-servarr/tinymediamanager -f myvalues.yaml

Uninstallation

To uninstall/delete the tinymediamanager deployment:

helm uninstall tinymediamanager

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.