Redmine

Redmine is a free and open source, web-based project management and issue tracking tool.

TL;DR;

$ helm install stable/redmine

Introduction

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

It also packages the Bitnami MariaDB chart and the PostgreSQL chart which are required for bootstrapping a MariaDB/PostgreSQL deployment for the database requirements of the Redmine application.

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/redmine

The command deploys Redmine 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.

Using PostgreSQL instead of MariaDB

This chart includes the option to use a PostgreSQL database for Redmine instead of MariaDB. To use this, MariaDB must be explicitly disabled and PostgreSQL enabled:

helm install --name my-release stable/redmine --set databaseType.mariadb=false,databaseType.postgresql=true

Configuration

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

Parameter	Description	Default
image	Redmine image	bitnami/redmine:{VERSION}
imagePullPolicy	Image pull policy	IfNotPresent
redmineUsername	User of the application	user
redminePassword	Application password	random 10 character long alphanumeric string
redmineEmail	Admin email	user@example.com
redmineLanguage	Redmine default data language	en
extraVars	Environment variables, passed to redmine	nil
smtpHost	SMTP host	nil
smtpPort	SMTP port	nil
smtpUser	SMTP user	nil
smtpPassword	SMTP password	nil
smtpTls	Use TLS encryption with SMTP	nil
databaseType.postgresql	Select postgresql database	false
databaseType.mariadb	Select mariadb database	true
mariadb.mariadbRootPassword	MariaDB admin password	nil
postgresql.postgresqlPassword	PostgreSQL admin password	nil
serviceType	Kubernetes Service type	LoadBalancer
serviceLoadBalancerSourceRanges	An array of load balancer sources	0.0.0.0/0
ingress.enabled	Enable or disable the ingress	false
ingress.hostname	The virtual host name	redmine.cluster.local
ingress.annotations	An array of service annotations	nil
`ingress.tls[i].secretName	The secret kubernetes.io/tls	nil
`ingress.tls[i].hosts[j]	The virtual host name	nil
networkPolicyApiVersion	The kubernetes network API version	extensions/v1beta1
persistence.enabled	Enable persistence using PVC	true
persistence.existingClaim	The name of an existing PVC	nil
persistence.storageClass	PVC Storage Class	nil (uses alpha storage class annotation)
persistence.accessMode	PVC Access Mode	ReadWriteOnce
persistence.size	PVC Storage Request	8Gi

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

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

$ helm install --name my-release \
  --set redmineUsername=admin,redminePassword=password,mariadb.mariadbRootPassword=secretpassword \
    stable/redmine

The above command sets the Redmine 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 --name my-release -f values.yaml stable/redmine

Tip: You can use the default values.yaml

Persistence

The Bitnami Redmine image stores the Redmine data and configurations at the /bitnami/redmine 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. The volume is created using dynamic volume provisioning. Clusters configured with NFS mounts require manually managed volumes and claims.

See the Configuration section to configure the PVC or to disable persistence.

Existing PersistentVolumeClaims

The following example includes two PVCs, one for redmine and another for Maria DB.

1. Create the PersistentVolume
2. Create the PersistentVolumeClaim
3. Create the directory, on a worker
4. Install the chart

$ helm install --name test --set persistence.existingClaim=PVC_REDMINE,mariadb.persistence.existingClaim=PVC_MARIADB  redmine