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.

Prerequisites

Kubernetes 1.4+ with Beta APIs enabled
PV provisioner support in the underlying infrastructure

Installing the Chart

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

$ helm install --name my-release stable/parse

The command deploys Parse on the Kubernetes cluster in the default configuration. The configuration 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.

Configuration

The following table lists the configurable parameters of the Parse chart and their default values.

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`
`nameOverride`	String to partially override parse.fullname template with a string (will prepend the release name)	`nil`
`fullnameOverride`	String to fully override parse.fullname template with a string	`nil`
`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	`docker.io`
`volumePermissions.image.repository`	Init container volume-permissions image name	`bitnami/minideb`
`volumePermissions.image.tag`	Init container volume-permissions image tag	`stretch`
`volumePermissions.image.pullPolicy`	Init container volume-permissions image pull policy	`Always`
`volumePermissions.resources`	Init container resource requests/limit	`nil`
`service.type`	Kubernetes Service type	`LoadBalancer`
`service.port`	Service HTTP port (Dashboard)	`80`
`service.loadBalancerIP`	`loadBalancerIP` for the Parse Service	`nil`
`service.externalTrafficPolicy`	Enable client source IP preservation	`Cluster`
`service.nodePorts.http`	Kubernetes http node port	`""`
`server.image.registry`	Parse image registry	`docker.io`
`server.image.repository`	Parse image name	`bitnami/parse`
`server.image.tag`	Parse image tag	`{TAG_NAME}`
`server.image.pullPolicy`	Image pull policy	`IfNotPresent`
`server.image.pullSecrets`	Specify docker-registry secret names as an array	`[]` (does not add image pull secrets to deployed pods)
`server.securityContext.enabled`	Enable security context for Parse Server	`true`
`server.securityContext.fsGroup`	Group ID for Parse Server container	`1001`
`server.securityContext.runAsUser`	User ID for Parse Server container	`1001`
`server.host`	Hostname to use to access Parse server (when `ingress.enabled=true` is set to `ingress.server.hosts[0].name` by default)	`nil`
`server.port`	Parse server port	`1337`
`server.mountPath`	Parse server API mount path	`/parse`
`server.appId`	Parse server App Id	`myappID`
`server.masterKey`	Parse server Master Key	`random 10 character alphanumeric string`
`server.resources`	CPU/Memory resource requests/limits	Memory: `512Mi`, CPU: `300m`
`dashboard.enabled`	Enable parse dashboard	`true`
`dashboard.image.registry`	Dashboard image registry	`docker.io`
`dashboard.image.repository`	Dashboard image name	`bitnami/parse-dashboard`
`dashboard.image.tag`	Dashboard image tag	`{TAG_NAME}`
`dashboard.image.pullPolicy`	Image pull policy	`IfNotPresent`
`dashboard.securityContext.enabled`	Enable security context for Dashboard	`true`
`dashboard.securityContext.fsGroup`	Group ID for Dashboard container	`1001`
`dashboard.securityContext.runAsUser`	User ID for Dashboard container	`1001`
`dashboard.image.pullSecrets`	Specify docker-registry secret names as an array	`[]` (does not add image pull secrets to deployed pods)
`dashboard.username`	Dashboard username	`user`
`dashboard.password`	Dashboard user password	`random 10 character alphanumeric string`
`dashboard.appName`	Dashboard application name	`MyDashboard`
`dashboard.resources`	CPU/Memory resource requests/limits	Memory: `512Mi`, CPU: `300m`
`persistence.enabled`	Enable Parse persistence using PVC	`true`
`persistence.storageClass`	PVC Storage Class for Parse volume	`nil` (uses alpha storage class annotation)
`persistence.accessMode`	PVC Access Mode for Parse volume	`ReadWriteOnce`
`persistence.size`	PVC Storage Request for Parse volume	`8Gi`
`ingress.enabled`	Enable ingress controller resource	`false`
`ingress.annotations`	Ingress annotations	`[]`
`ingress.certManager`	Add annotations for cert-manager	`false`
`ingress.dashboard.hosts[0].name`	Hostname to your Parse Dashboard installation	`ghost.local`
`ingress.dashboard.hosts[0].path`	Path within the url structure	`/`
`ingress.dashboard.hosts[0].tls`	Utilize TLS backend in ingress	`false`
`ingress.dashboard.hosts[0].tlsHosts`	Array of TLS hosts for ingress record (defaults to `ingress.hosts[0].name` if `nil`)	`nil`
`ingress.dashboard.hosts[0].tlsSecret`	TLS Secret (certificates)	`ghost.local-tls-secret`
`ingress.server.hosts[0].name`	Hostname to your Parse Server installation	`ghost.local`
`ingress.server.hosts[0].path`	Path within the url structure	`/`
`ingress.server.hosts[0].tls`	Utilize TLS backend in ingress	`false`
`ingress.server.hosts[0].tlsHosts`	Array of TLS hosts for ingress record (defaults to `ingress.hosts[0].name` if `nil`)	`nil`
`ingress.server.hosts[0].tlsSecret`	TLS Secret (certificates)	`ghost.local-tls-secret`
`ingress.secrets[0].name`	TLS Secret Name	`nil`
`ingress.secrets[0].certificate`	TLS Secret Certificate	`nil`
`ingress.secrets[0].key`	TLS Secret Key	`nil`
`mongodb.usePassword`	Enable MongoDB password authentication	`true`
`mongodb.password`	MongoDB admin password	`nil`
`mongodb.persistence.enabled`	Enable MongoDB persistence using PVC	`true`
`mongodb.persistence.storageClass`	PVC Storage Class for MongoDB volume	`nil` (uses alpha storage class annotation)
`mongodb.persistence.accessMode`	PVC Access Mode for MongoDB volume	`ReadWriteOnce`
`mongodb.persistence.size`	PVC Storage Request for MongoDB volume	`8Gi`

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

Note

:

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

Optionally, you can specify the loadBalancerIP parameter to assign a reserved IP address to the Parse 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 parse-public-ip
The reserved IP address can be associated to the Parse service by specifying it as the value of the loadBalancerIP parameter while installing the chart.

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

$ helm install --name my-release \
  --set dashboard.username=admin,dashboard.password=password \
    stable/parse

The above command sets the Parse administrator account username and password to admin and password respectively.

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 stable/parse

Tip

: You can use the default values.yaml

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.

Persistence

The Bitnami Parse image stores the Parse data and configurations at the /bitnami/parse 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 Configuration section to configure the PVC or to disable persistence.

Adjust permissions of persistent volume mountpoint

As the image run as non-root by default, it is necessary to adjust the ownership of the persistent volume so that the container can write data into it.

By default, the chart is configured to use Kubernetes Security Context to automatically change the ownership of the volume. However, this feature does not work in all Kubernetes distributions. As an alternative, this chart supports using an initContainer to change the ownership of the volume before mounting it in the final destination.

You can enable this initContainer by setting volumePermissions.enabled to true.

Upgrading

To 5.1.0

Parse & Parse Dashboard containers were moved to a non-root approach. There shouldn't be any issue when upgrading since the corresponding securityContext is enabled by default. Both container images and chart can be upgraded by running the command below:

$ helm upgrade my-release stable/parse

If you use a previous container image (previous to 3.1.2-r14 for Parse or 1.2.0-r69 for Parse Dashboard), disable the securityContext by running the command below:

$ helm upgrade my-release stable/parse --set server.securityContext.enabled=fase,dashboard.securityContext.enabled=fase,server.image.tag=XXX,dashboard.image.tag=YYY

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 parse:

$ kubectl patch deployment parse-parse-dashboard --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
$ kubectl patch deployment parse-parse-server --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
$ kubectl patch deployment parse-mongodb --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'