You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
132 lines
3.3 KiB
YAML
132 lines
3.3 KiB
YAML
# Default values for wordpress.
|
|
# This is a YAML-formatted file.
|
|
# Declare variables to be passed into your templates.
|
|
|
|
replicaCount: 2
|
|
|
|
image:
|
|
repository: wordpress
|
|
pullPolicy: IfNotPresent
|
|
# Overrides the image tag whose default is the chart appVersion.
|
|
tag: "6.6.2"
|
|
|
|
imagePullSecrets: []
|
|
nameOverride: ""
|
|
fullnameOverride: ""
|
|
|
|
serviceAccount:
|
|
# Specifies whether a service account should be created
|
|
create: true
|
|
# Annotations to add to the service account
|
|
annotations: {}
|
|
# The name of the service account to use.
|
|
# If not set and create is true, a name is generated using the fullname template
|
|
name: ""
|
|
|
|
env:
|
|
WORDPRESS_DB_HOST: wp_dbhost
|
|
WORDPRESS_DB_USER: wp_user
|
|
WORDPRESS_DB_NAME: wb_database
|
|
|
|
podAnnotations: {}
|
|
|
|
podSecurityContext: {}
|
|
# fsGroup: 2000
|
|
|
|
securityContext: {}
|
|
# capabilities:
|
|
# drop:
|
|
# - ALL
|
|
# # readOnlyRootFilesystem: true
|
|
# runAsNonRoot: true
|
|
# runAsUser: 1000
|
|
|
|
service:
|
|
type: ClusterIP
|
|
port: 80
|
|
|
|
ingress:
|
|
enabled: false
|
|
annotations: {}
|
|
# kubernetes.io/ingress.class: nginx
|
|
# kubernetes.io/tls-acme: "true"
|
|
hosts:
|
|
- host: chart-example.local
|
|
paths: []
|
|
tls: []
|
|
# - secretName: chart-example-tls
|
|
# hosts:
|
|
# - chart-example.local
|
|
|
|
resources:
|
|
# We usually recommend not to specify default resources and to leave this as a conscious
|
|
# choice for the user. This also increases chances charts run on environments with little
|
|
# resources, such as Minikube. If you do want to specify resources, uncomment the following
|
|
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
|
|
limits:
|
|
cpu: 2000m
|
|
memory: 512Mi
|
|
requests:
|
|
cpu: 250m
|
|
memory: 128Mi
|
|
|
|
autoscaling:
|
|
enabled: true
|
|
minReplicas: 2
|
|
maxReplicas: 10
|
|
targetCPUUtilizationPercentage: 80
|
|
# targetMemoryUtilizationPercentage: 80
|
|
|
|
nodeSelector: {}
|
|
|
|
tolerations: []
|
|
|
|
affinity: {}
|
|
|
|
wordpressScheme: http
|
|
|
|
livenessProbe:
|
|
enabled: true
|
|
httpGet:
|
|
path: /wp-admin/install.php
|
|
port: '{{ .Values.wordpressScheme }}'
|
|
scheme: '{{ .Values.wordpressScheme | upper }}'
|
|
## If using an HTTPS-terminating load-balancer, the probes may need to behave
|
|
## like the balancer to prevent HTTP 302 responses. According to the Kubernetes
|
|
## docs, 302 should be considered "successful", but this issue on GitHub
|
|
## (https://github.com/kubernetes/kubernetes/issues/47893) shows that it isn't.
|
|
## E.g.
|
|
## httpHeaders:
|
|
## - name: X-Forwarded-Proto
|
|
## value: https
|
|
##
|
|
httpHeaders: []
|
|
initialDelaySeconds: 120
|
|
periodSeconds: 10
|
|
timeoutSeconds: 5
|
|
failureThreshold: 6
|
|
successThreshold: 1
|
|
|
|
readinessProbe:
|
|
enabled: true
|
|
httpGet:
|
|
#path: /wp-login.php
|
|
path: /?nocache
|
|
port: '{{ .Values.wordpressScheme }}'
|
|
scheme: '{{ .Values.wordpressScheme | upper }}'
|
|
## If using an HTTPS-terminating load-balancer, the probes may need to behave
|
|
## like the balancer to prevent HTTP 302 responses. According to the Kubernetes
|
|
## docs, 302 should be considered "successful", but this issue on GitHub
|
|
## (https://github.com/kubernetes/kubernetes/issues/47893) shows that it isn't.
|
|
## E.g.
|
|
## httpHeaders:
|
|
## - name: X-Forwarded-Proto
|
|
## value: https
|
|
##
|
|
httpHeaders: []
|
|
initialDelaySeconds: 30
|
|
periodSeconds: 10
|
|
timeoutSeconds: 5
|
|
failureThreshold: 6
|
|
successThreshold: 1
|