1## Bitnami WordPress image version
2## ref: https://hub.docker.com/r/bitnami/wordpress/tags/
3##
4image:
5 registry: docker.io
6 repository: bitnami/wordpress
7 tag: 4.9.8-debian-9
8 ## Specify a imagePullPolicy
9 ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
10 ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
11 ##
12 pullPolicy: IfNotPresent
13 ## Optionally specify an array of imagePullSecrets.
14 ## Secrets must be manually created in the namespace.
15 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
16 ##
17 # pullSecrets:
18 # - myRegistrKeySecretName
19
20## User of the application
21## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
22##
23wordpressUsername: user
24
25## Application password
26## Defaults to a random 10-character alphanumeric string if not set
27## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
28##
29# wordpressPassword:
30
31## Admin email
32## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
33##
34wordpressEmail: user@example.com
35
36## First name
37## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
38##
39wordpressFirstName: FirstName
40
41## Last name
42## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
43##
44wordpressLastName: LastName
45
46## Blog name
47## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
48##
49wordpressBlogName: User's Blog!
50
51## Table prefix
52## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
53##
54wordpressTablePrefix: wp_
55
56## Set to `yes` to allow the container to be started with blank passwords
57## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
58allowEmptyPassword: yes
59
60## SMTP mail delivery configuration
61## ref: https://github.com/bitnami/bitnami-docker-wordpress/#smtp-configuration
62##
63# smtpHost:
64# smtpPort:
65# smtpUser:
66# smtpPassword:
67# smtpUsername:
68# smtpProtocol:
69
70replicaCount: 1
71
72externalDatabase:
73## All of these values are only used when mariadb.enabled is set to false
74 ## Database host
75 host: localhost
76
77 ## non-root Username for Wordpress Database
78 user: bn_wordpress
79
80 ## Database password
81 password: ""
82
83 ## Database name
84 database: bitnami_wordpress
85
86 ## Database port number
87 port: 3306
88
89##
90## MariaDB chart configuration
91##
92mariadb:
93 ## Whether to deploy a mariadb server to satisfy the applications database requirements. To use an external database set this to false and configure the externalDatabase parameters
94 enabled: true
95 ## Disable MariaDB replication
96 replication:
97 enabled: false
98
99 ## Create a database and a database user
100 ## ref: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#creating-a-database-user-on-first-run
101 ##
102 db:
103 name: bitnami_wordpress
104 user: bn_wordpress
105 ## If the password is not specified, mariadb will generates a random password
106 ##
107 # password:
108
109 ## MariaDB admin password
110 ## ref: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#setting-the-root-password-on-first-run
111 ##
112 # rootUser:
113 # password:
114
115 ## Enable persistence using Persistent Volume Claims
116 ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
117 ##
118 master:
119 persistence:
120 enabled: true
121 ## mariadb data Persistent Volume Storage Class
122 ## If defined, storageClassName: <storageClass>
123 ## If set to "-", storageClassName: "", which disables dynamic provisioning
124 ## If undefined (the default) or set to null, no storageClassName spec is
125 ## set, choosing the default provisioner. (gp2 on AWS, standard on
126 ## GKE, AWS & OpenStack)
127 ##
128 # storageClass: "-"
129 accessMode: ReadWriteOnce
130 size: 8Gi
131
132## Kubernetes configuration
133## For minikube, set this to NodePort, elsewhere use LoadBalancer or ClusterIP
134##
135serviceType: LoadBalancer
136##
137## serviceType: NodePort
138## nodePorts:
139## http: <to set explicitly, choose port between 30000-32767>
140## https: <to set explicitly, choose port between 30000-32767>
141nodePorts:
142 http: ""
143 https: ""
144## Enable client source IP preservation
145## ref http://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
146##
147serviceExternalTrafficPolicy: Cluster
148
149## Allow health checks to be pointed at the https port
150healthcheckHttps: false
151
152## Configure extra options for liveness and readiness probes
153## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
154livenessProbe:
155 initialDelaySeconds: 120
156 periodSeconds: 10
157 timeoutSeconds: 5
158 failureThreshold: 6
159 successThreshold: 1
160readinessProbe:
161 initialDelaySeconds: 30
162 periodSeconds: 10
163 timeoutSeconds: 5
164 failureThreshold: 6
165 successThreshold: 1
166
167## Configure the ingress resource that allows you to access the
168## Wordpress installation. Set up the URL
169## ref: http://kubernetes.io/docs/user-guide/ingress/
170##
171ingress:
172 ## Set to true to enable ingress record generation
173 enabled: false
174
175 ## The list of hostnames to be covered with this ingress record.
176 ## Most likely this will be just one host, but in the event more hosts are needed, this is an array
177 hosts:
178 - name: wordpress.local
179
180 ## Set this to true in order to enable TLS on the ingress record
181 ## A side effect of this will be that the backend wordpress service will be connected at port 443
182 tls: false
183
184 ## If TLS is set to true, you must declare what secret will store the key/certificate for TLS
185 tlsSecret: wordpress.local-tls
186
187 ## Ingress annotations done as key:value pairs
188 ## If you're using kube-lego, you will want to add:
189 ## kubernetes.io/tls-acme: true
190 ##
191 ## For a full list of possible ingress annotations, please see
192 ## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/annotations.md
193 ##
194 ## If tls is set to true, annotation ingress.kubernetes.io/secure-backends: "true" will automatically be set
195 annotations:
196 # kubernetes.io/ingress.class: nginx
197 # kubernetes.io/tls-acme: true
198
199 secrets:
200 ## If you're providing your own certificates, please use this to add the certificates as secrets
201 ## key and certificate should start with -----BEGIN CERTIFICATE----- or
202 ## -----BEGIN RSA PRIVATE KEY-----
203 ##
204 ## name should line up with a tlsSecret set further up
205 ## If you're using kube-lego, this is unneeded, as it will create the secret for you if it is not set
206 ##
207 ## It is also possible to create and manage the certificates outside of this helm chart
208 ## Please see README.md for more information
209 # - name: wordpress.local-tls
210 # key:
211 # certificate:
212
213## Enable persistence using Persistent Volume Claims
214## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
215##
216persistence:
217 enabled: true
218 ## wordpress data Persistent Volume Storage Class
219 ## If defined, storageClassName: <storageClass>
220 ## If set to "-", storageClassName: "", which disables dynamic provisioning
221 ## If undefined (the default) or set to null, no storageClassName spec is
222 ## set, choosing the default provisioner. (gp2 on AWS, standard on
223 ## GKE, AWS & OpenStack)
224 ##
225 # storageClass: "-"
226 ##
227 ## If you want to reuse an existing claim, you can pass the name of the PVC using
228 ## the existingClaim variable
229 # existingClaim: your-claim
230 accessMode: ReadWriteOnce
231 size: 10Gi
232
233## Configure resource requests and limits
234## ref: http://kubernetes.io/docs/user-guide/compute-resources/
235##
236resources:
237 requests:
238 memory: 512Mi
239 cpu: 300m
240
241## Node labels for pod assignment
242## Ref: https://kubernetes.io/docs/user-guide/node-selection/
243##
244nodeSelector: {}
245
246## Tolerations for pod assignment
247## Ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
248##
249tolerations: []
250
251## Affinity for pod assignment
252## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
253##
254affinity: {}
View as plain text