Files
deprecated-helm-charts/stable/wordpress/values.yaml
T
Bruno e0db20e829 [stable/wordpress] Use only one PVC to prevent zone conflicts (#689)
* Use only one PVC

* Syntax fix & version bump

* [stable/redis] add persistence.existingClaim (#717)

* add persistence.existingClaim to redis

* missed the version

* cleanup templating

* [stable/prometheus] Fixed server ingress annotations (#853)

* Fixed server ingress annotations

* Version bump

* Update GitLab-CE image to release 9.0.0 (#827)

* Update GitLab-CE image to release 9.0.0

* Update dependencies version

* Change username from admin to root

* [stable/drupal] Release 0.4.6 (#831)

* drupal: update to `bitnami/drupal:8.2.7-r1`

* drupal: bump chart version to `0.4.6`

* Add OWNERS file, Fix #753 (#792)

* [stable/testlink] Release 0.4.6 (#851)

* testlink: update to `bitnami/testlink:1.9.16-r3`

* testlink: bump chart version to `0.4.6`

* [stable/mariadb] Release 0.5.14 (#830)

* mariadb: update to `bitnami/mariadb:10.1.22-r1`

* mariadb: bump chart version to `0.5.14`

* Updated Artifactory version to 5.1.0 (#725)

* Upgraded artifactory version to 4.16.0

* changes as per suggestion

* [stable/wordpress] Release 0.5.2 (#850)

* wordpress: update to `bitnami/wordpress:4.7.3-r2`

* wordpress: bump chart version to `0.5.2`

* [stable/owncloud] Release 0.4.6 (#848)

* owncloud: update to `bitnami/owncloud:9.1.4-r2`

* owncloud: bump chart version to `0.4.6`

* [stable/odoo] Release 0.4.4 (#842)

* odoo: update to `bitnami/odoo:10.0.20170317-r1`

* odoo: bump chart version to `0.4.4`

* [stable/moodle] Release 0.1.3 (#846)

* moodle: update to `bitnami/moodle:3.2.1-r4`

* moodle: updated chart requirements

* moodle: bump chart version to `0.1.3`

* moodle: update to `bitnami/moodle:3.2.2-r0`
2017-04-05 10:56:42 -07:00

137 lines
3.7 KiB
YAML

## Bitnami WordPress image version
## ref: https://hub.docker.com/r/bitnami/wordpress/tags/
##
image: bitnami/wordpress:4.7.3-r2
## Specify a imagePullPolicy
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##
imagePullPolicy: IfNotPresent
## User of the application
## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
##
wordpressUsername: user
## Application password
## Defaults to a random 10-character alphanumeric string if not set
## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
##
# wordpressPassword:
## Admin email
## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
##
wordpressEmail: user@example.com
## First name
## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
##
wordpressFirstName: FirstName
## Last name
## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
##
wordpressLastName: LastName
## Blog name
## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
##
wordpressBlogName: User's Blog!
## Set to `yes` to allow the container to be started with blank passwords
## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
allowEmptyPassword: yes
## SMTP mail delivery configuration
## ref: https://github.com/bitnami/bitnami-docker-wordpress/#smtp-configuration
##
# smtpHost:
# smtpPort:
# smtpUser:
# smtpPassword:
# smtpUsername:
# smtpProtocol:
##
## MariaDB chart configuration
##
mariadb:
## MariaDB admin password
## ref: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#setting-the-root-password-on-first-run
##
# mariadbRootPassword:
## Create a database
## ref: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#creating-a-database-on-first-run
##
mariadbDatabase: bitnami_wordpress
## Create a database user
## ref: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#creating-a-database-user-on-first-run
##
mariadbUser: bn_wordpress
## Password for mariadbUser
## ref: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#creating-a-database-user-on-first-run
##
# mariadbPassword:
## Enable persistence using Persistent Volume Claims
## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
##
persistence:
enabled: true
## If defined, volume.beta.kubernetes.io/storage-class: <storageClass>
## Default: volume.alpha.kubernetes.io/storage-class: default
##
# storageClass:
accessMode: ReadWriteOnce
size: 8Gi
## Kubernetes configuration
## For minikube, set this to NodePort, elsewhere use LoadBalancer
##
serviceType: LoadBalancer
## Configure ingress resource that allow you to access the
## Wordpress instalation. Set up the URL
## ref: http://kubernetes.io/docs/user-guide/ingress/
##
ingress:
enabled: false
hostname: wordpress.local
## Ingress annotations
##
# annotations:
# kubernetes.io/ingress.class: nginx
## Ingress TLS configuration
## Secrets must be manually created in the namespace
##
# tls:
# - secretName: wordpress.local-tls
# hosts:
# - wordpress.local
## Enable persistence using Persistent Volume Claims
## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
##
persistence:
enabled: true
## If defined, volume.beta.kubernetes.io/storage-class: <storageClass>
## Default: volume.alpha.kubernetes.io/storage-class: default
##
# storageClass:
accessMode: ReadWriteOnce
size: 10Gi
## Configure resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
resources:
requests:
memory: 512Mi
cpu: 300m