[bitnami/wordpress] Add TLS parameter to values.yaml and schema (#2628)

* Add TLS setting to values.yaml and the schema
This commit is contained in:
Andres Martinez Gotor
2020-05-21 10:10:34 +02:00
committed by GitHub
parent 035148374b
commit 0153daf820
5 changed files with 35 additions and 3 deletions

View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: wordpress
version: 9.3.2
version: 9.3.3
appVersion: 5.4.1
description: Web publishing platform for building blogs and websites.
icon: https://bitnami.com/assets/stacks/wordpress/img/wordpress-stack-220x234.png

View File

@@ -153,6 +153,7 @@ The following table lists the configurable parameters of the WordPress chart and
| `ingress.enabled` | Enable ingress controller resource | `false` |
| `ingress.certManager` | Add annotations for cert-manager | `false` |
| `ingress.hostname` | Default host for the ingress resource | `wordpress.local` |
| `ingress.tls` | Create TLS Secret | `false` |
| `ingress.annotations` | Ingress annotations | `[]` (evaluated as a template) |
| `ingress.extraHosts[0].name` | Additional hostnames to be covered | `nil` |
| `ingress.extraHosts[0].path` | Additional hostnames to be covered | `nil` |

View File

@@ -14,7 +14,7 @@
image:
registry: docker.io
repository: bitnami/wordpress
tag: 5.4.1-debian-10-r19
tag: 5.4.1-debian-10-r20
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -306,6 +306,12 @@ ingress:
##
annotations: {}
## Enable TLS configuration for the hostname defined at ingress.hostname parameter
## TLS certificates will be retrieved from a TLS secret with name: {{- printf "%s-tls" .Values.ingress.hostname }}
## You can use the ingress.secrets parameter to create this TLS secret or relay on cert-manager to create it
##
tls: false
## The list of additional hostnames to be covered with this ingress record.
## Most likely the hostname above will be enough, but in the event more hosts are needed, this is an array
## extraHosts:

View File

@@ -130,6 +130,25 @@
"condition": false,
"value": "ingress.enabled"
}
},
"certManager": {
"type": "boolean",
"form": true,
"title": "Enable CertManager",
"description": "This will add the required annotation for CertManager to add certificates.",
"hidden": {
"condition": false,
"value": "ingress.enabled"
}
},
"tls": {
"type": "boolean",
"form": true,
"title": "Create a TLS secret",
"hidden": {
"condition": false,
"value": "ingress.enabled"
}
}
}
},

View File

@@ -14,7 +14,7 @@
image:
registry: docker.io
repository: bitnami/wordpress
tag: 5.4.1-debian-10-r19
tag: 5.4.1-debian-10-r20
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -306,6 +306,12 @@ ingress:
##
annotations: {}
## Enable TLS configuration for the hostname defined at ingress.hostname parameter
## TLS certificates will be retrieved from a TLS secret with name: {{- printf "%s-tls" .Values.ingress.hostname }}
## You can use the ingress.secrets parameter to create this TLS secret or relay on cert-manager to create it
##
tls: false
## The list of additional hostnames to be covered with this ingress record.
## Most likely the hostname above will be enough, but in the event more hosts are needed, this is an array
## extraHosts: