Chart version: 2.2.4
Api version: v1
App version: v3.0.4892-ls61
DEPRECATED - Want a Movie or TV Show on Plex or Emby? Use Ombi!
Chart Type
Set me up:
helm repo add center
Install Chart:
helm install ombi center/billimek/ombi
Versions (0)


This chart has been deprecated and moved to its new home:

helm repo add k8s-at-home
helm install k8s-at-home/ombi

This is a helm chart for Ombi leveraging the image


$ helm repo add billimek
$ helm install billimek/ombi

Installing the Chart

To install the chart with the release name my-release:

helm install --name my-release billimek/ombi

Uninstalling the Chart

To uninstall/delete the my-release deployment:

helm delete my-release --purge

The command removes all the Kubernetes components associated with the chart and deletes the release.


The following tables lists the configurable parameters of the Sentry chart and their default values.

Parameter Description Default
image.repository Image repository linuxserver/ombi
image.tag Image tag. Possible values listed here. 3.0.4914-ls72
image.pullPolicy Image pull policy IfNotPresent
strategyType Specifies the strategy used to replace old Pods by new ones Recreate
timezone Timezone the Ombi instance should run as, e.g. ‘America/New_York’ UTC
puid process userID the Ombi instance should run as 1001
pgid process groupID the Ombi instance should run as 1001
baseUrl adjust baseUrl if behind a reverse proxy null
probes.liveness.initialDelaySeconds Specify liveness initialDelaySeconds parameter for the deployment 60
probes.liveness.failureThreshold Specify liveness failureThreshold parameter for the deployment 5
probes.liveness.timeoutSeconds Specify liveness timeoutSeconds parameter for the deployment 10
probes.readiness.initialDelaySeconds Specify readiness initialDelaySeconds parameter for the deployment 60
probes.readiness.failureThreshold Specify readiness failureThreshold parameter for the deployment 5
probes.readiness.timeoutSeconds Specify readiness timeoutSeconds parameter for the deployment 10
Service.type Kubernetes service type for the Ombi GUI ClusterIP
Service.port Kubernetes port where the Ombi GUI is exposed 3579
Service.annotations Service annotations for the Ombi GUI {}
Service.labels Custom labels {}
Service.loadBalancerIP Loadbalance IP for the Ombi GUI {}
Service.loadBalancerSourceRanges List of IP CIDRs allowed access to load balancer (if supported) None
ingress.enabled Enables Ingress false
ingress.annotations Ingress annotations {}
ingress.labels Custom labels {}
ingress.path Ingress path /
ingress.hosts Ingress accepted hostnames chart-example.local
ingress.tls Ingress TLS configuration []
persistence.config.enabled Use persistent volume to store configuration data true
persistence.config.size Size of persistent volume claim 1Gi
persistence.config.existingClaim Use an existing PVC to persist data nil
persistence.config.subPath Mount a sub directory of the persistent volume if set ""
persistence.config.storageClass Type of persistent volume claim -
persistence.config.accessMode Persistence access mode ReadWriteOnce
persistence.config.skipuninstall Do not delete the pvc upon helm uninstall false
resources CPU/Memory resource requests/limits {}
nodeSelector Node labels for pod assignment {}
tolerations Toleration labels for pod assignment []
affinity Affinity settings for pod assignment {}
podAnnotations Key-value pairs to add as pod annotations {}
deploymentAnnotations Key-value pairs to add as deployment annotations {}

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

helm install --name my-release \
  --set timezone="America/New York" \

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

helm install --name my-release -f values.yaml billimek/ombi


If you get Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: ... it may be because you uninstalled the chart with skipuninstall enabled, you need to manually delete the pvc or use existingClaim.

Read through the values.yaml file. It has several commented out suggested values.