Skip to main content

Values

This document describes the configurable values for the WordPress Helm chart.

Configuration Options​

The WordPress chart supports various configuration options through values. You can customize the deployment by creating a values.yaml file or passing values directly via the --set flag.

Example​

To install with custom values:

helm install <release-name> welance-charts/wordpress -f values.yaml

Or using --set:

helm install <release-name> welance-charts/wordpress --set key=value

Default Values​

The following is the default values.yaml file for the WordPress Helm chart:

# Default values for helm-chart.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1

db:
hostname: welance-noprod-serverlessv2-tf.cluster-ccr9p5q6kxw9.eu-central-1.rds.amazonaws.com
port: 3306
database: p217-01-develop
username: p217-01-develop
password: "<your-database-password>"

dump:
image: registry.gitlab.com/welance/platform/pipelines/container/images/mysql-backup:0.0.3
enabled: false
schedule: "0 2 * * *"
s3:
bucket: s3://welance-backup-storage/
accessKeyId: "<your-s3-access-key-id>"
secretAccessKey: "<your-s3-secret-access-key>"
region: de
endpoint: https://s3.de.io.cloud.ovh.net

tls: []

externalService:
enabled: true # default is true

##TO BE OVERRIDDEN
storage:
gid: 1000
uid: 1000
fid: fs-0e7fcf2d3c61da878a

image:
repository: registry.gitlab.com/welance/p222-choco/p222-01-choco.com
pullPolicy: IfNotPresent
tag: "dev"
imagePullSecrets: regcred
commit:
sha: ""
url: ""
branch: ""

configmap:
enabled: true

# Default value for config file content
envFileContent: ""

basicAuthSecret:
enabled: true
data:
auth: "<your-basic-auth-secret>"

registryAuthSecret:
name: regcred
data:
auth: "<your-registry-auth-secret>"

nfs:
enabled: false
storageclassName: ""

deployment:
nodeSelector: {}
securityContext:
enabled: true
runAsUser: 33
runAsGroup: 33
fsGroup: 33
annotations: {}
env:
ABSPATH: /var/www/
port:
name: http
containerPort: 8080
protocol: TCP
volumes:
- name: uploads
mountPath: /var/www/wp-content/uploads
storage:
path: "/var/www/wp-content/uploads"

liveness:
enabled: false
readiness:
enabled: false
startup:
enabled: false

service:
name: service-web
type: ClusterIP
port: 80
targetPort: 8080


ingresses:
redirect: []
live:
enabled: false
sites: []
web:
name: ingress-web
enabled: true
ingressClassName: "welance-develop"
annotations: {}

resources: {}
# limits:
# cpu: 50m
# memory: 1500Mi
# requests:
# cpu: 25m
# memory: 300Mi

redis:
image:
repository: "redis"
tag: "5-alpine"
resources:
limits:
cpu: 25m
memory: 265Mi
requests:
cpu: 25m
memory: 265Mi

quota:
enabled: false
hard:
requests.cpu: "1"
requests.memory: 4Gi
limits.cpu: "2"
limits.memory: 6Gi

autoscaling:
enabled: false
minReplicas: 1
maxReplicas: 100
targetCPUUtilizationPercentage: 80
targetMemoryUtilizationPercentage: 80

Key Configuration Sections​

Database Configuration (db)​

  • Database connection settings including hostname, port, database name, username, and password

Image Configuration (image)​

  • Container image repository, tag, pull policy, and image pull secrets
  • Git commit information (SHA, URL, branch)

Deployment Configuration (deployment)​

  • Security context settings
  • Environment variables (WordPress absolute path: ABSPATH: /var/www/)
  • Container port configuration (8080)
  • Volume mounts for WordPress uploads (/var/www/wp-content/uploads)
  • Health check probes (liveness, readiness, startup - all disabled by default)

Service & Ingress (service, ingresses)​

  • Service type and port configuration (port 80, target port 8080)
  • Ingress settings

Resources & Scaling​

  • Resource limits and requests (commented example: 50m CPU, 1500Mi memory limits)
  • Redis configuration
  • Resource quotas (higher defaults: 4Gi requests, 6Gi limits memory)
  • Horizontal Pod Autoscaling (HPA) settings

Storage & Backup​

  • NFS storage configuration
  • Database dump/backup settings with S3 integration (MySQL backup)
  • WordPress uploads directory mounted as volume

WordPress-Specific Notes​

  • Uploads Directory: WordPress uploads are stored in /var/www/wp-content/uploads and mounted as a persistent volume
  • Absolute Path: The ABSPATH environment variable is set to /var/www/ for WordPress
  • Service Port: Service exposes port 80 but targets container port 8080
  • Resource Requirements: WordPress typically requires more memory than other applications (example shows 1500Mi limit)