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