From e34cebdc357c2f28e3ec466dee53529f1d2e33ca Mon Sep 17 00:00:00 2001 From: Miguel Ruiz Date: Thu, 26 May 2022 12:11:36 +0200 Subject: [PATCH] [bitnami/logstash] Add missing values (#10421) * [bitnami/logstash] Add missing service parameters Signed-off-by: Miguel Ruiz * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers Co-authored-by: Bitnami Containers --- bitnami/logstash/Chart.yaml | 2 +- bitnami/logstash/README.md | 7 +++++-- bitnami/logstash/values.yaml | 19 +++++++++++++++++++ 3 files changed, 25 insertions(+), 3 deletions(-) diff --git a/bitnami/logstash/Chart.yaml b/bitnami/logstash/Chart.yaml index 04ff9d7fd..e365441cc 100644 --- a/bitnami/logstash/Chart.yaml +++ b/bitnami/logstash/Chart.yaml @@ -23,4 +23,4 @@ name: logstash sources: - https://github.com/bitnami/bitnami-docker-logstash - https://www.elastic.co/products/logstash -version: 5.0.4 +version: 5.0.5 diff --git a/bitnami/logstash/README.md b/bitnami/logstash/README.md index d75f9df50..2e69504f8 100644 --- a/bitnami/logstash/README.md +++ b/bitnami/logstash/README.md @@ -82,7 +82,7 @@ The command removes all the Kubernetes components associated with the chart and | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------ | | `image.registry` | Logstash image registry | `docker.io` | | `image.repository` | Logstash image repository | `bitnami/logstash` | -| `image.tag` | Logstash image tag (immutable tags are recommended) | `8.2.0-debian-10-r0` | +| `image.tag` | Logstash image tag (immutable tags are recommended) | `8.2.1-debian-10-r0` | | `image.pullPolicy` | Logstash image pull policy | `IfNotPresent` | | `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` | | `image.debug` | Specify if debug logs should be enabled | `false` | @@ -162,6 +162,8 @@ The command removes all the Kubernetes components associated with the chart and | `service.externalTrafficPolicy` | External traffic policy, configure to Local to preserve client source IP when using an external loadBalancer | `""` | | `service.clusterIP` | Static clusterIP or None for headless services | `""` | | `service.annotations` | Annotations for Logstash service | `{}` | +| `service.sessionAffinity` | Session Affinity for Kubernetes service, can be "None" or "ClientIP" | `None` | +| `service.sessionAffinityConfig` | Additional settings for the sessionAffinity | `{}` | | `persistence.enabled` | Enable Logstash data persistence using PVC | `false` | | `persistence.existingClaim` | A manually managed Persistent Volume and Claim | `""` | | `persistence.storageClass` | PVC Storage Class for Logstash data volume | `""` | @@ -169,11 +171,12 @@ The command removes all the Kubernetes components associated with the chart and | `persistence.size` | PVC Storage Request for Logstash data volume | `2Gi` | | `persistence.annotations` | Annotations for the PVC | `{}` | | `persistence.mountPath` | Mount path of the Logstash data volume | `/bitnami/logstash/data` | +| `persistence.selector` | Selector to match an existing Persistent Volume for WordPress data PVC | `{}` | | `volumePermissions.enabled` | Enable init container that changes the owner and group of the persistent volume(s) mountpoint to `runAsUser:fsGroup` | `false` | | `volumePermissions.securityContext.runAsUser` | User ID for the volumePermissions init container | `0` | | `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` | | `volumePermissions.image.repository` | Init container volume-permissions image repository | `bitnami/bitnami-shell` | -| `volumePermissions.image.tag` | Init container volume-permissions image tag (immutable tags are recommended) | `10-debian-10-r414` | +| `volumePermissions.image.tag` | Init container volume-permissions image tag (immutable tags are recommended) | `10-debian-10-r434` | | `volumePermissions.image.pullPolicy` | Init container volume-permissions image pull policy | `IfNotPresent` | | `volumePermissions.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` | | `volumePermissions.resources.limits` | Init container volume-permissions resource limits | `{}` | diff --git a/bitnami/logstash/values.yaml b/bitnami/logstash/values.yaml index f662aee12..c10df37fc 100644 --- a/bitnami/logstash/values.yaml +++ b/bitnami/logstash/values.yaml @@ -451,6 +451,17 @@ service: ## @param service.annotations Annotations for Logstash service ## annotations: {} + ## @param service.sessionAffinity Session Affinity for Kubernetes service, can be "None" or "ClientIP" + ## If "ClientIP", consecutive client requests will be directed to the same Pod + ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies + ## + sessionAffinity: None + ## @param service.sessionAffinityConfig Additional settings for the sessionAffinity + ## sessionAffinityConfig: + ## clientIP: + ## timeoutSeconds: 300 + ## + sessionAffinityConfig: {} ## Persistence parameters ## persistence: @@ -482,6 +493,14 @@ persistence: ## @param persistence.mountPath Mount path of the Logstash data volume ## mountPath: /bitnami/logstash/data + ## @param persistence.selector Selector to match an existing Persistent Volume for WordPress data PVC + ## If set, the PVC can't have a PV dynamically provisioned for it + ## E.g. + ## selector: + ## matchLabels: + ## app: my-app + ## + selector: {} ## Init Container parameters ## Change the owner and group of the persistent volume(s) mountpoint(s) to 'runAsUser:fsGroup' on each component ## values from the securityContext section of the component