Skip to content

Latest commit

 

History

History
96 lines (82 loc) · 24.6 KB

README.md

File metadata and controls

96 lines (82 loc) · 24.6 KB

Jira Software

Atlassian Jira Software built for every member of your software team to plan, track, and release great software.

Installing the Chart

Before you can install the chart you will need to add the stevehipwell repo to Helm.

helm repo add stevehipwell https://stevehipwell.github.io/helm-charts/

After you've installed the repo you can install the chart.

helm upgrade --install --namespace default --values ./my-values.yaml my-release stevehipwell/jira-software

Configuration

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

Parameter Description Default
image.repository Image repository. atlassian/jira-software
image.tag Image tag. {{ .Chart.AppVersion }}-jdk11
image.pullPolicy Image pull policy. IfNotPresent
imagePullSecrets Image pull secrets. []
nameOverride Override the name of the chart. null
fullnameOverride Override the fullname of the chart. null
commonLabels Labels to add to all chart resources. {}
serviceAccount.create If true, create a new service account. true
serviceAccount.annotations Annotations to add to the service account. {}
serviceAccount.name Service account to be used. If not set and serviceAccount.create is true, a name is generated using the fullname template. null
serviceAccount.automountToken If true, mount the ServiceAccount token. false
deployment If true, a Deployment will be created instead of a StatefulSet. Set this to true if you're migrating from a version < v5.0.0 and leave it set to false if you're starting with a version >= v5.0.0. IMPORTANT - Do not change this value after setting it, you could loose your data. false
podLabels Labels to add to the pod. {}
podAnnotations Annotations to add to the pod. {}
podSecurityContext Security context for the pod. {fsGroup: 2001}
securityContext Security context for the jira container. {}
priorityClassName Priority class name to use. ""
livenessProbe The liveness probe. See values.yaml
readinessProbe The readiness probe. See values.yaml
service.type Service type. ClusterIP
service.clusterIP Service cluster IP. null
service.annotations Annotations to add to the service. {}
service.port Service port. 443
ingress.enabled If true, create an ingress object. false
ingress.annotations Ingress annotations. {}
ingress.ingressClassName Ingress class to use. ""
ingress.hosts Ingress hosts. []
ingress.tls Ingress TLS configuration []
persistence.enabled If true, create a PVC. false
persistence.annotations Annotations to add to the PVC. {}
persistence.existingClaim Use an existing PVC to persist data. null
persistence.accessMode Persistence access mode. ReadWriteOnce
persistence.storageClass PVC storage class (use - for default). standard
persistence.size Size of PVC to create. 8Gi
persistence.retainDeleted If true and deployment: false, keep the PVC when the StatefulSet is deleted. true
resources Resource requests and limits for the the jira container. {}
terminationGracePeriodSeconds Termination grace period in seconds. 30
nodeSelector Node labels for pod assignment. {}
affinity Affinity settings for pod assignment. If an explicit label selector is not provided for pod affinity or pod anti-affinity one will be created from the pod selector labels. {}
topologySpreadConstraints Topology spread constraints for pod assignment. If an explicit label selector is not provided one will be created from the pod selector labels. []
tolerations Tolerations for pod assignment. []
caCerts.enabled If true, add provided CA certificates to the JVM cacerts key store. false
caCerts.secret Secret containing the additional CA certificates. null
envVars.jvmMinHeapSize JVM min heap size to set as JVM_MINIMUM_MEMORY (documentation). 384m
envVars.jvmMaxHeapSize JVM max heap size to set as JVM_MAXIMUM_MEMORY (documentation). 768m
envVars.jvmReservedCodeCacheSize JVM reserved code cache size to set as JVM_RESERVED_CODE_CACHE_SIZE (documentation). 1024m
envVars.jvmAdditionalMemoryOptions Additional JVM memory options. -XX:+UseG1GC
envVars.jvmAdditionalOptions Additional JVM options. ""
envVars.forceCfgUpdate If the configuration is re-created every time the pod starts (documentation). false
envVars.setPermissions If the home directory permissions are set at startup (documentation). ""
env Environment variables for the jira container. []
extraVolumeMounts Additional volume mounts for the jira container. []
extraInitContainers Additional init containers for the pod. []
extraVolumes Additional volumes for the pod. []
psql.host External PostgreSQL host to use (if this is set the additional psql values need to be set) null
psql.port External PostgreSQL port null
psql.database External PostgreSQL database null
psql.username External PostgreSQL username null
psql.password.secret Name of the secret containing the external PostgreSQL password null
psql.password.key Key on the secret containing the external PostgreSQL password null
postgresql.enabled Enable PostgreSQL sub chart, see chart for additional values. false

Database

By default the atlassian/jira-software image will create a H2 database for evaluation purposes, this should NOT be used in production. You can either allow this chart to create a PostgreSQL instance specifically for Jira Software by specifying postgresql.enabled as true or you can use an external PostgreSQL instance by specifying the connection details on psql.

Persistence

The atlassian/jira-software image stores the Jira Software data and configurations at the /var/atlassian/application-data/jira path in 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.