Chart version: 10.0.1
Api version: v2
App version: 10.6.0
A file sharing server that puts the control and security of you...
Chart Type
Set me up:
helm repo add center
Install Chart:
helm install owncloud center/bitnami/owncloud
Versions (0)


ownCloud is a file sharing server that puts the control and security of your own data back into your hands.


$ helm repo add bitnami
$ helm install my-release bitnami/owncloud


This chart bootstraps an ownCloud deployment on a Kubernetes cluster using the Helm package manager.

It also packages the Bitnami MariaDB chart which is required for bootstrapping a MariaDB deployment for the database requirements of the ownCloud application.

Bitnami charts can be used with Kubeapps for deployment and management of Helm Charts in clusters. This chart has been tested to work with NGINX Ingress, cert-manager, fluentd and Prometheus on top of the BKPR.


  • Kubernetes 1.12+
  • Helm 3.0-beta3+
  • PV provisioner support in the underlying infrastructure
  • ReadWriteMany volumes for deployment scaling

Installing the Chart

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

$ helm install my-release bitnami/owncloud

The command deploys ownCloud on the Kubernetes cluster in the default configuration. The Parameters section lists the parameters that can be configured during installation.

Tip: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

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


The following table lists the configurable parameters of the ownCloud chart and their default values per section/component:

Global parameters

Parameter Description Default
global.imageRegistry Global Docker image registry nil
global.imagePullSecrets Global Docker registry secret names as an array [] (does not add image pull secrets to deployed pods)
global.storageClass Global storage class for dynamic provisioning nil

Common parameters

Parameter Description Default
image.registry ownCloud image registry
image.repository ownCloud Image name bitnami/owncloud
image.tag ownCloud Image tag {TAG_NAME}
image.pullPolicy ownCloud image pull policy IfNotPresent
image.pullSecrets Specify docker-registry secret names as an array [] (does not add image pull secrets to deployed pods)
image.debug Specify if debug logs should be enabled false
nameOverride String to partially override owncloud.fullname template nil
fullnameOverride String to fully override owncloud.fullname template nil
commonLabels Labels to add to all deployed objects nil
commonAnnotations Annotations to add to all deployed objects []
extraDeploy Array of extra objects to deploy with the release (evaluated as a template). nil

ownCloud parameters

Parameter Description Default
affinity Map of node/pod affinities {}
allowEmptyPassword Allow DB blank passwords yes
args Override default container args (useful when using custom images) nil
command Override default container command (useful when using custom images) nil
containerPorts.http Sets http port inside NGINX container 8080
containerPorts.https Sets https port inside NGINX container 8443
containerSecurityContext.enabled Enable ownCloud containers’ Security Context true
containerSecurityContext.runAsUser ownCloud containers’ Security Context 1001
customLivenessProbe Override default liveness probe nil
customReadinessProbe Override default readiness probe nil
customStartupProbe Override default startup probe nil
existingSecret Name of a secret with the application password nil
extraEnvVarsCM ConfigMap containing extra env vars nil
extraEnvVarsSecret Secret containing extra env vars (in case of sensitive data) nil
extraEnvVars Extra environment variables nil
extraVolumeMounts Array of extra volume mounts to be added to the container (evaluated as template). Normally used with extraVolumes. nil
extraVolumes Array of extra volumes to be added to the deployment (evaluated as template). Requires setting extraVolumeMounts nil
initContainers Add additional init containers to the pod (evaluated as a template) nil
lifecycleHooks LifecycleHook to set additional configuration at startup Evaluated as a template
livenessProbe Liveness probe configuration Check values.yaml file
nodeAffinityPreset.type Node affinity preset type. Ignored if affinity is set. Allowed values: soft or hard ""
nodeAffinityPreset.key Node label key to match Ignored if affinity is set. ""
nodeAffinityPreset.values Node label values to match. Ignored if affinity is set. []
nodeSelector Node labels for pod assignment {} (The value is evaluated as a template)
owncloudHost ownCloud host to create application URLs (when ingress, it will be ignored) nil
owncloudUsername User of the application user
owncloudPassword Application password random 10 character alphanumeric string
owncloudEmail Admin email
owncloudSkipInstall Skip ownCloud installation wizard (no / yes) false
podAffinityPreset Pod affinity preset. Ignored if affinity is set. Allowed values: soft or hard ""
podAntiAffinityPreset Pod anti-affinity preset. Ignored if affinity is set. Allowed values: soft or hard soft
podAnnotations Pod annotations {}
podLabels Add additional labels to the pod (evaluated as a template) nil
podSecurityContext.enabled Enable ownCloud pods’ Security Context true
podSecurityContext.fsGroup ownCloud pods’ group ID 1001
readinessProbe Readiness probe configuration Check values.yaml file
replicaCount Number of ownCloud Pods to run 1
resources CPU/Memory resource requests/limits Memory: 512Mi, CPU: 300m
sidecars Attach additional containers to the pod (evaluated as a template) nil
smtpHost SMTP host nil
smtpPort SMTP port nil (but owncloud internal default is 25)
smtpProtocol SMTP Protocol (options: ssl,tls, nil) nil
smtpUser SMTP user nil
smtpPassword SMTP password nil
startupProbe Startup probe configuration Check values.yaml file
tolerations Tolerations for pod assignment [] (The value is evaluated as a template)
updateStrategy Deployment update strategy nil

Database parameters

Parameter Description Default
mariadb.enabled Whether to use the MariaDB chart true
mariadb.architecture MariaDB architecture (standalone or replication) standalone
mariadb.auth.rootPassword Password for the MariaDB root user random 10 character alphanumeric string
mariadb.auth.database Database name to create bitnami_owncloud
mariadb.auth.username Database user to create bn_owncloud
mariadb.auth.password Password for the database random 10 character long alphanumeric string
mariadb.primary.persistence.enabled Enable database persistence using PVC true
mariadb.primary.persistence.existingClaim Name of an existing PersistentVolumeClaim for MariaDB primary replicas nil
mariadb.primary.persistence.accessModes Database Persistent Volume Access Modes [ReadWriteOnce]
mariadb.primary.persistence.size Database Persistent Volume Size 8Gi
mariadb.primary.persistence.hostPath Set path in case you want to use local host path volumes (not recommended in production) nil
mariadb.primary.persistence.storageClass MariaDB primary persistent volume storage Class nil
externalDatabase.user Existing username in the external db bn_owncloud
externalDatabase.password Password for the above username ""
externalDatabase.database Name of the existing database bitnami_owncloud Host of the existing database nil
externalDatabase.port Port of the existing database 3306

Persistence parameters

Parameter Description Default
persistence.enabled Enable persistence using PVC true
persistence.storageClass PVC Storage Class for ownCloud volume nil (uses alpha storage class annotation)
persistence.existingClaim An Existing PVC name for ownCloud volume nil (uses alpha storage class annotation)
persistence.hostPath Host mount path for ownCloud volume nil (will not mount to a host path)
persistence.accessMode PVC Access Mode for ownCloud volume ReadWriteOnce
persistence.size PVC Storage Request for ownCloud volume 8Gi

Volume Permissions parameters

Parameter Description Default
volumePermissions.enabled Enable init container that changes volume permissions in the data directory (for cases where the default k8s runAsUser and fsUser values do not work) false
volumePermissions.image.registry Init container volume-permissions image registry
volumePermissions.image.repository Init container volume-permissions image name bitnami/minideb
volumePermissions.image.tag Init container volume-permissions image tag buster
volumePermissions.image.pullSecrets Specify docker-registry secret names as an array [] (does not add image pull secrets to deployed pods)
volumePermissions.image.pullPolicy Init container volume-permissions image pull policy Always
volumePermissions.resources Init container resource requests/limit nil

Traffic Exposure Parameters

Parameter Description Default
service.type Kubernetes Service type LoadBalancer
service.loadBalancerIP Kubernetes LoadBalancerIP to request LoadBalancer
service.port Service HTTP port 80
service.httpsPort Service HTTPS port 443
service.externalTrafficPolicy Enable client source IP preservation Cluster
service.nodePorts.http Kubernetes http node port ""
service.nodePorts.https Kubernetes https node port ""
ingress.enabled Enable ingress controller resource false
ingress.certManager Add annotations for cert-manager false
ingress.hostname Default host for the ingress resource owncloud.local
ingress.tls Enable TLS for ingress.hostname parameter false
ingress.annotations Ingress annotations {}
ingress.extraHosts[0].name Hostname to your ownCloud installation nil
ingress.extraHosts[0].path Path within the url structure nil
ingress.extraTls[0].hosts[0] TLS configuration for additional hosts nil
ingress.extraTls[0].secretName TLS Secret (certificates) nil
ingress.secrets[0].name TLS Secret Name nil
ingress.secrets[0].certificate TLS Secret Certificate nil
ingress.secrets[0].key TLS Secret Key nil

Metrics parameters

Parameter Description Default
metrics.enabled Start a side-car prometheus exporter false
metrics.image.registry Apache exporter image registry
metrics.image.repository Apache exporter image name bitnami/apache-exporter
metrics.image.tag Apache exporter image tag {TAG_NAME}
metrics.image.pullPolicy Image pull policy IfNotPresent
metrics.image.pullSecrets Specify docker-registry secret names as an array [] (does not add image pull secrets to deployed pods)
metrics.service.type Prometheus metrics service type LoadBalancer
metrics.service.port Service Metrics port 9117
metrics.service.annotations Annotations for enabling prometheus scraping { "true", "9117"}
metrics.resources Exporter resource requests/limit {}

Certificate injection parameters

Parameter Description Default
certificates.customCertificate.certificateSecret Secret containing the certificate and key to add "" Name of the secret containing the certificate chain ""
certificates.customCertificate.chainSecret.key Key of the certificate chain file inside the secret ""
certificates.customCertificate.certificateLocation Location in the container to store the certificate /etc/ssl/certs/ssl-cert-snakeoil.pem
certificates.customCertificate.keyLocation Location in the container to store the private key /etc/ssl/private/ssl-cert-snakeoil.key
certificates.customCertificate.chainLocation Location in the container to store the certificate chain /etc/ssl/certs/chain.pem
certificates.customCAs Defines a list of secrets to import into the container trust store []
certificates.image.registry Container sidecar registry
certificates.image.repository Container sidecar image bitnami/minideb
certificates.image.tag Container sidecar image tag buster
certificates.image.pullPolicy Container sidecar image pull policy IfNotPresent
certificates.image.pullSecrets Container sidecar image pull secrets image.pullSecrets
certificates.args Override default container args (useful when using custom images) nil
certificates.command Override default container command (useful when using custom images) nil
certificates.extraEnvVars Container sidecar extra environment variables (eg proxy) []
certificates.extraEnvVarsCM ConfigMap containing extra env vars nil
certificates.extraEnvVarsSecret Secret containing extra env vars (in case of sensitive data) nil

The above parameters map to the env variables defined in bitnami/owncloud. For more information please refer to the bitnami/owncloud image documentation.


For ownCloud to function correctly, you should specify the owncloudHost parameter to specify the FQDN (recommended) or the public IP address of the ownCloud service.

Optionally, you can specify the owncloudLoadBalancerIP parameter to assign a reserved IP address to the ownCloud service of the chart. However please note that this feature is only available on a few cloud providers (f.e. GKE).

To reserve a public IP address on GKE:

> $ gcloud compute addresses create owncloud-public-ip
> ```
> The reserved IP address can be associated to the ownCloud service by specifying it as the value of the `owncloudLoadBalancerIP` parameter while installing the chart.

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

$ helm install my-release \
  --set owncloudUsername=admin,owncloudPassword=password,mariadb.auth.rootPassword=secretpassword \

The above command sets the ownCloud administrator account username and password to admin and password respectively. Additionally, it sets the MariaDB root user password to secretpassword.

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

$ helm install my-release -f values.yaml bitnami/owncloud

Tip: You can use the default values.yaml

Configuration and installation details

Rolling VS Immutable tags

It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.

Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.


The image parameter allows specifying which image will be pulled for the chart.

Private registry

If you configure the image value to one in a private registry, you will need to specify an image pull secret.

  1. Manually create image pull secret(s) in the namespace. See this YAML example reference. Consult your image registry’s documentation about getting the appropriate secret.

  2. Note that the imagePullSecrets configuration value cannot currently be passed to helm using the --set parameter, so you must supply these using a values.yaml file, such as:

    ”`yaml imagePullSecrets:

    • name: SECRET_NAME 1. Install the chart ### Setting Pod's affinity This chart allows you to set your custom affinity using the `affinity` paremeter. Find more infomation about Pod's affinity in the [kubernetes documentation]( As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common]( chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters. ## Persistence The [Bitnami ownCloud]( image stores the ownCloud data and configurations at the `/bitnami/owncloud` path of the container. Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube. See the [Parameters](#parameters) section to configure the PVC or to disable persistence. ### Existing PersistentVolumeClaim 1. Create the PersistentVolume 1. Create the PersistentVolumeClaim 1. Install the chart bash $ helm install my-release –set persistence.existingClaim=PVC_NAME bitnami/owncloud “`

Host path

System compatibility

  • The local filesystem accessibility to a container in a pod with hostPath has been tested on OSX/MacOS with xhyve, and Linux with VirtualBox.
  • Windows has not been tested with the supported VM drivers. Minikube does however officially support Mounting Host Folders per pod. Or you may manually sync your container whenever host files are changed with tools like docker-sync or docker-bg-sync.

Mounting steps

  1. The specified hostPath directory must already exist (create one if it does not).

  2. Install the chart

    $ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT bitnami/owncloud

    This will mount the owncloud-data volume into the hostPath directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch. 1. Because the container cannot control the host machine’s directory permissions, you must set the ownCloud file directory permissions yourself and disable or clear ownCloud cache.

    CA Certificates

    Custom CA certificates not included in the base docker image can be added by means of existing secrets. The secret must exist in the same namespace and contain the desired CA certificates to import. By default, all found certificate files will be loaded.

    - secret: my-ca-1
    - secret: my-ca-2

Tip! You can create a secret containing your CA certificates using the following command:

kubectl create secret generic my-ca-1 --from-file my-ca-1.crt


Find more information about how to deal with common errors related to Bitnami’s Helm charts in this troubleshooting guide.


To 10.0.0

In this major there were three main changes introduced:

  • Parameter standarizations
  • Migration to non-root

To upgrade to 8.0.0, backup ownCloud data and the previous MariaDB databases, install a new ownCloud chart and import the backups and data, ensuring the 1001 user has the appropriate permissions on the migrated volume.

1. Chart standarizations

This upgrade adapts the chart to the latest Bitnami good practices. Check the Parameters section for more information. In summary:

  • Lots of new parameters were added, including SMTP configuration, for using existing DBs (owncloudSkipInstall), configuring security context, etc.
  • Some parameters were renamed or disappeared in favor of new ones in this major version. For example, persistence.owncloud.* parameters were deprecated in favor of persistence.*.
  • This version also introduces bitnami/common, a library chart as a dependency. More documentation about this new utility could be found here. Please, make sure that you have updated the chart dependencies before executing any upgrade.

2. Migration of the ownCloud image to non-root

The Bitnami ownCloud image was migrated to a “non-root” user approach. Previously the container ran as the root user and the Apache daemon was started as the daemon user. From now on, both the container and the Apache daemon run as user 1001. Consequences:

  • The HTTP/HTTPS ports exposed by the container are now 8080/8443 instead of 80/443.
  • Backwards compatibility is not guaranteed. Uninstall & install the chart again to obtain the latest version.

You can revert this behavior by setting the parameters containerSecurityContext.runAsUser to root.

To 9.0.0

In this major there were two main changes introduced:

  1. Adaptation to Helm v2 EOL
  2. Updated MariaDB dependency version

Please read the update notes carefully.

1. Adaptation to Helm v2 EOL

On November 13, 2020, Helm v2 support was formally finished, this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.

What changes were introduced in this major version?

  • Previous versions of this Helm Chart use apiVersion: v1 (installable by both Helm 2 and 3), this Helm Chart was updated to apiVersion: v2 (installable by Helm 3 only). Here you can find more information about the apiVersion field.
  • Move dependency information from the requirements.yaml to the Chart.yaml
  • After running helm dependency update, a Chart.lock file is generated containing the same structure used in the previous requirements.lock
  • The different fields present in the Chart.yaml file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts

Considerations when upgrading to this version

  • If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn’t face any issues
  • If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn’t support Helm v2 anymore
  • If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the official Helm documentation about migrating from Helm v2 to v3

Useful links

2. Updated MariaDB dependency version

In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check MariaDB Upgrading Notes for more information.

To upgrade to 9.0.0, it should be done reusing the PVCs used to hold both the MariaDB and ownCloud data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is owncloud and that a rootUser.password was defined for MariaDB in values.yaml when the chart was first installed):

NOTE: Please, create a backup of your database before running any of those actions. The steps below would be only valid if your application (e.g. any plugins or custom code) is compatible with MariaDB 10.5.x

Obtain the credentials and the names of the PVCs used to hold both the MariaDB and ownCloud data on your current release:

export OWNCLOUD_HOST=$(kubectl get svc --namespace default owncloud --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
export OWNCLOUD_PASSWORD=$(kubectl get secret --namespace default owncloud -o jsonpath="{.data.owncloud-password}" | base64 --decode)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default owncloud-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 --decode)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default owncloud-mariadb -o jsonpath="{.data.mariadb-password}" | base64 --decode)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=owncloud -o jsonpath="{.items[0]}")

Delete the ownCloud deployment and delete the MariaDB statefulset. Notice the option --cascade=false in the latter:

$ kubectl delete deployments.apps owncloud

$ kubectl delete statefulsets.apps owncloud-mariadb --cascade=false

Now the upgrade works:

$ helm upgrade owncloud bitnami/owncloud --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set owncloudPassword=$OWNCLOUD_PASSWORD --set owncloudHost=$OWNCLOUD_HOST

You will have to delete the existing MariaDB pod and the new statefulset is going to create a new one

$ kubectl delete pod owncloud-mariadb-0

Finally, you should see the lines below in MariaDB container logs:

$ kubectl logs $(kubectl get pods -l,, -o jsonpath="{.items[0]}")
mariadb 12:13:24.98 INFO  ==> Using persisted data
mariadb 12:13:25.01 INFO  ==> Running mysql_upgrade


Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes’ point of view, so you cannot “upgrade” those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.

In the apiVersion of the deployment resources was updated to apps/v1 in tune with the api’s deprecated, resulting in compatibility breakage.

This major version signifies this change.

To 3.0.0

Backwards compatibility is not guaranteed unless you modify the labels used on the chart’s deployments. Use the workaround below to upgrade from versions previous to 3.0.0. The following example assumes that the release name is owncloud:

$ kubectl patch deployment owncloud-owncloud --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
$ kubectl delete statefulset owncloud-mariadb --cascade=false