[bitnami/*] Fix nil values for Elasticsearch and Kibana (#7393)

This commit is contained in:
Miguel Ruiz
2021-09-02 18:40:18 +02:00
committed by GitHub
parent dbf7f041f1
commit e8eba199ba
6 changed files with 27 additions and 27 deletions

View File

@@ -25,4 +25,4 @@ name: elasticsearch
sources:
- https://github.com/bitnami/bitnami-docker-elasticsearch
- https://www.elastic.co/products/elasticsearch
version: 16.0.1
version: 16.0.2

View File

@@ -90,17 +90,17 @@ $ helm delete --purge my-release
| `security.tls.restEncryption` | Enable SSL/TLS encryption for Elasticsearch REST API. | `true` |
| `security.tls.autoGenerated` | Create self-signed TLS certificates. | `false` |
| `security.tls.verificationMode` | Verification mode for SSL communications. | `full` |
| `security.tls.master.existingSecret` | Existing secret containing the certificates for the master nodes | `nil` |
| `security.tls.data.existingSecret` | Existing secret containing the certificates for the data nodes | `nil` |
| `security.tls.ingest.existingSecret` | Existing secret containing the certificates for the ingest nodes | `nil` |
| `security.tls.coordinating.existingSecret` | Existing secret containing the certificates for the coordinating nodes | `nil` |
| `security.tls.master.existingSecret` | Existing secret containing the certificates for the master nodes | `""` |
| `security.tls.data.existingSecret` | Existing secret containing the certificates for the data nodes | `""` |
| `security.tls.ingest.existingSecret` | Existing secret containing the certificates for the ingest nodes | `""` |
| `security.tls.coordinating.existingSecret` | Existing secret containing the certificates for the coordinating nodes | `""` |
| `security.tls.keystorePassword` | Password to access the JKS/PKCS12 keystore or PEM key when they are password-protected. | `""` |
| `security.tls.truststorePassword` | Password to access the JKS/PKCS12 truststore when they are password-protected. | `""` |
| `security.tls.keystoreFilename` | Name of the keystore file | `elasticsearch.keystore.jks` |
| `security.tls.truststoreFilename` | Name of the truststore | `elasticsearch.truststore.jks` |
| `security.tls.usePemCerts` | Use this variable if your secrets contain PEM certificates instead of JKS/PKCS12 | `false` |
| `security.tls.keyPassword` | Password to access the PEM key when they are password-protected. | `""` |
| `name` | Elasticsearch cluster name | `elastic` |
| `name` | Elasticsearch cluster name | `""` |
| `plugins` | Comma, semi-colon or space separated list of plugins to install at initialization | `""` |
| `snapshotRepoPath` | File System snapshot repository path | `""` |
| `config` | Override elasticsearch configuration | `{}` |
@@ -369,7 +369,7 @@ $ helm delete --purge my-release
| `ingest.service.port` | Kubernetes Service port Elasticsearch transport port (ingest nodes) | `9300` |
| `ingest.service.nodePort` | Kubernetes Service nodePort (ingest nodes) | `""` |
| `ingest.service.annotations` | Annotations for ingest nodes service | `{}` |
| `ingest.service.loadBalancerIP` | loadBalancerIP if ingest nodes service type is `LoadBalancer` | `nil` |
| `ingest.service.loadBalancerIP` | loadBalancerIP if ingest nodes service type is `LoadBalancer` | `""` |
| `ingest.serviceAccount.create` | Create a default serviceaccount for elasticsearch curator | `false` |
| `ingest.serviceAccount.name` | Name of the created serviceAccount | `""` |

View File

@@ -120,13 +120,13 @@ security:
## @param security.tls.coordinating.existingSecret Existing secret containing the certificates for the coordinating nodes
##
master:
existingSecret:
existingSecret: ""
data:
existingSecret:
existingSecret: ""
ingest:
existingSecret:
existingSecret: ""
coordinating:
existingSecret:
existingSecret: ""
## @param security.tls.keystorePassword Password to access the JKS/PKCS12 keystore or PEM key when they are password-protected.
##
keystorePassword: ""
@@ -1106,7 +1106,7 @@ ingest:
## @param ingest.service.loadBalancerIP loadBalancerIP if ingest nodes service type is `LoadBalancer`
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
##
loadBalancerIP:
loadBalancerIP: ""
## Provide functionality to use RBAC
##

View File

@@ -25,4 +25,4 @@ name: kibana
sources:
- https://github.com/bitnami/bitnami-docker-kibana
- https://www.elastic.co/products/kibana
version: 9.0.0
version: 9.0.1

View File

@@ -76,7 +76,7 @@ The command removes all the Kubernetes components associated with the chart and
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| `image.registry` | Kibana image registry | `docker.io` |
| `image.repository` | Kibana image repository | `bitnami/kibana` |
| `image.tag` | Kibana image tag (immutable tags are recommended) | `7.14.0-debian-10-r0` |
| `image.tag` | Kibana image tag (immutable tags are recommended) | `7.14.1-debian-10-r0` |
| `image.pullPolicy` | Kibana image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `replicaCount` | Number of replicas of the Kibana Pod | `1` |
@@ -96,7 +96,7 @@ The command removes all the Kubernetes components associated with the chart and
| `volumePermissions.enabled` | Enable init container that changes volume permissions in the data directory (for cases where the default k8s `runAsUser` and `fsUser` values do not work) | `false` |
| `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` |
| `volumePermissions.image.repository` | Init container volume-permissions image name | `bitnami/bitnami-shell` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag | `10-debian-10-r172` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag | `10-debian-10-r180` |
| `volumePermissions.image.pullPolicy` | Init container volume-permissions image pull policy | `Always` |
| `volumePermissions.image.pullSecrets` | Init container volume-permissions image pull secrets | `[]` |
| `volumePermissions.resources` | Volume Permissions resources | `{}` |
@@ -177,7 +177,7 @@ The command removes all the Kubernetes components associated with the chart and
| ---------------------- | ------------------------------------------------------------------------------ | ------- |
| `tls.enabled` | Enable SSL/TLS encryption for Kibana server (HTTPS) | `false` |
| `tls.autoGenerated` | Create self-signed TLS certificates. Currently only supports PEM certificates. | `false` |
| `tls.existingSecret` | Name of the existing secret containing Kibana server certificates | `nil` |
| `tls.existingSecret` | Name of the existing secret containing Kibana server certificates | `""` |
| `tls.usePemCerts` | Use this variable if your secrets contain PEM certificates instead of PKCS12 | `false` |
| `tls.keyPassword` | Password to access the PEM key when it is password-protected. | `""` |
| `tls.keystorePassword` | Password to access the PKCS12 keystore when it is password-protected. | `""` |
@@ -192,14 +192,14 @@ The command removes all the Kubernetes components associated with the chart and
| `elasticsearch.port` | Elasticsearch port | `""` |
| `elasticsearch.security.auth.enabled` | Set to 'true' if Elasticsearch has authentication enabled | `false` |
| `elasticsearch.security.auth.kibanaUsername` | Kibana server user to authenticate with Elasticsearch | `elastic` |
| `elasticsearch.security.auth.kibanaPassword` | Kibana server password to authenticate with Elasticsearch | `nil` |
| `elasticsearch.security.auth.existingSecret` | Name of the existing secret containing the Password for the Kibana user | `nil` |
| `elasticsearch.security.auth.kibanaPassword` | Kibana server password to authenticate with Elasticsearch | `""` |
| `elasticsearch.security.auth.existingSecret` | Name of the existing secret containing the Password for the Kibana user | `""` |
| `elasticsearch.security.tls.enabled` | Set to 'true' if Elasticsearch API uses TLS/SSL (HTTPS) | `false` |
| `elasticsearch.security.tls.verificationMode` | Verification mode for SSL communications. | `full` |
| `elasticsearch.security.tls.existingSecret` | Name of the existing secret containing Elasticsearch Truststore or CA certificate. Required unless verificationMode=none | `nil` |
| `elasticsearch.security.tls.existingSecret` | Name of the existing secret containing Elasticsearch Truststore or CA certificate. Required unless verificationMode=none | `""` |
| `elasticsearch.security.tls.usePemCerts` | Set to 'true' to use PEM certificates instead of PKCS12. | `false` |
| `elasticsearch.security.tls.truststorePassword` | Password to access the PKCS12 trustore in case it is password-protected. | `nil` |
| `elasticsearch.security.tls.passwordsSecret` | Name of a existing secret containing the Truststore password | `nil` |
| `elasticsearch.security.tls.truststorePassword` | Password to access the PKCS12 trustore in case it is password-protected. | `""` |
| `elasticsearch.security.tls.passwordsSecret` | Name of a existing secret containing the Truststore password | `""` |
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,

View File

@@ -492,7 +492,7 @@ tls:
autoGenerated: false
## @param tls.existingSecret Name of the existing secret containing Kibana server certificates
##
existingSecret:
existingSecret: ""
## @param tls.usePemCerts Use this variable if your secrets contain PEM certificates instead of PKCS12
## Note: Ignored when using autoGenerated certs.
##
@@ -531,10 +531,10 @@ elasticsearch:
kibanaUsername: "elastic"
## @param elasticsearch.security.auth.kibanaPassword Kibana server password to authenticate with Elasticsearch
##
kibanaPassword:
kibanaPassword: ""
## @param elasticsearch.security.auth.existingSecret Name of the existing secret containing the Password for the Kibana user
##
existingSecret:
existingSecret: ""
tls:
## @param elasticsearch.security.tls.enabled Set to 'true' if Elasticsearch API uses TLS/SSL (HTTPS)
##
@@ -545,13 +545,13 @@ elasticsearch:
verificationMode: "full"
## @param elasticsearch.security.tls.existingSecret Name of the existing secret containing Elasticsearch Truststore or CA certificate. Required unless verificationMode=none
##
existingSecret:
existingSecret: ""
## @param elasticsearch.security.tls.usePemCerts Set to 'true' to use PEM certificates instead of PKCS12.
##
usePemCerts: false
## @param elasticsearch.security.tls.truststorePassword Password to access the PKCS12 trustore in case it is password-protected.
##
truststorePassword:
truststorePassword: ""
## @param elasticsearch.security.tls.passwordsSecret Name of a existing secret containing the Truststore password
##
passwordsSecret:
passwordsSecret: ""