[{"_1":2,"_139":-5,"_140":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_27":28,"_29":30,"_59":60,"_61":-7,"_62":-7,"_63":-7,"_64":-7,"_65":-5,"_66":-5,"_67":11,"_68":11,"_52":69,"_123":21,"_91":92,"_124":90,"_125":51,"_35":36,"_126":11,"_127":21,"_128":129,"_130":-5,"_131":11,"_132":11},"scanningType","none","tagData",{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},"content_type","image","creator",29930447,"digest","sha256:097c7bbe3993f2a6a0d486773226a1bd5bf0d9afa9f03eef12b258c8a9f3c225","full_size",7947,"id",895270065,"images",[],"last_updated","2025-05-07T21:58:23.115363Z","last_updater","last_updater_username","bitnamirobot","media_type","application/vnd.oci.image.index.v1+json","name","sha256-4f06f6087176d13f0ecbe8b4f859c6915cd632d36de27bda202cd144c93991fe","repository",19064336,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_70":71,"_76":77,"_79":80,"_81":82,"_83":11,"_43":84,"_85":86,"_87":88,"_50":90,"_91":92,"_93":94,"_95":-5,"_96":97,"_98":99,"_100":101,"_102":-5,"_103":97,"_104":105,"_106":11,"_107":92,"_108":109,"_114":11,"_115":116,"_120":92,"_121":122},"categories",[72],{"_50":73,"_74":75},"Monitoring & observability","slug","monitoring-and-observability","content_types",[78,32],"helm","date_registered","2023-01-24T10:50:29.98947Z","description","Bitnami Helm chart for Logstash","is_private","2025-08-13T09:41:20.221072Z","last_modified","2026-03-12T07:23:00.990672Z","media_types",[89,49],"application/vnd.cncf.helm.config.v1+json","logstash","namespace","bitnamicharts","pull_count",1154430,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for Logstash\n\nLogstash is an open source data processing engine. It ingests data from multiple sources, processes it, and sends the output to final destination in real-time. It is a core component of the ELK stack.\n\n[Overview of Logstash](http://logstash.net)\n\nTrademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/logstash\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository.\n\n## Introduction\n\nThis chart bootstraps a [logstash](https://github.com/bitnami/containers/tree/main/bitnami/logstash) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n\n## Installing the Chart\n\nTo install the chart with the release name `my-release`:\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/logstash\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\nThese commands deploy logstash on the Kubernetes cluster in the default configuration. The [configuration](#configuration-and-installation-details) section lists the parameters that can be configured during installation.\n\n> **Tip**: List all releases using `helm list`\n\n## Configuration and installation details\n\nThis section describes credentials, configuration, and other installation options.\n\n### Resource requests and limits\n\nBitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.\n\nTo make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcesPreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).\n\n### [Rolling vs Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-understand-rolling-tags-containers-index.html)\n\nIt is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.\n\nBitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.\n\n### Expose the Logstash service\n\nThe service(s) created by the deployment can be exposed within or outside the cluster using any of the following approaches:\n\n- **Gateway API HTTPRoute**: Requires a Gateway API controller to be installed in the Kubernetes cluster. Set `httpRoute.enabled=true` to expose Logstash through HTTPRoute.\n- **Ingress**: This requires an Ingress controller to be installed in the Kubernetes cluster. Set `ingress.enabled=true` to expose the corresponding service(s) through Ingress.\n- **ClusterIP**: This exposes the service(s) on a cluster-internal IP address. This approach makes the corresponding service(s) reachable only from within the cluster. Set `service.type=ClusterIP` to choose this approach.\n- **NodePort**: This exposes the service() on each node's IP address at a static port (the NodePort). This approach makes the corresponding service(s) reachable from outside the cluster by requesting the static port using the node's IP address, such as *NODE-IP:NODE-PORT*. Set `service.type=NodePort` to choose this approach.\n- **LoadBalancer**: This exposes the service(s) externally using a cloud provider's load balancer. Set `service.type=LoadBalancer` to choose this approach.\n\n### Use custom configuration\n\nBy default, this Helm chart provides a basic configuration for Logstash: listening to HTTP requests on port 8080 and writing them to the standard output.\n\nThis Logstash configuration can be adjusted using the *input*, *filter*, and *output* parameters, which allow specification of the input, filter and output plugins configuration respectively. In addition to these options, the chart also supports reading configuration from an external ConfigMap via the *existingConfiguration* parameter. Note that this will override the parameters discussed previously.\n\n### Create and use multiple pipelines\n\nThe chart supports the use of [multiple pipelines](https://www.elastic.co/guide/en/logstash/master/multiple-pipelines.html) by setting the `enableMultiplePipelines` parameter to `true`.\n\nTo do this, place the `pipelines.yml` file in the `files/conf` directory, together with the rest of the desired configuration files. If the `enableMultiplePipelines` parameter is set to `true` but the `pipelines.yml` file does not exist in the mounted volume, a dummy file is created using the default configuration (a single pipeline).\n\nThe chart also supports setting an external ConfigMap with all the configuration filesvia the `existingConfiguration` parameter.\n\nHere is an example of creating multiple pipelines using a ConfigMap:\n\n- Create a ConfigMap with the configuration files:\n\n ```bash\n $ cat bye.conf\n input {\n file {\n path => \"/tmp/bye\"\n }\n }\n output {\n stdout { }\n }\n\n $ cat hello.conf\n input {\n file {\n path => \"/tmp/hello\"\n }\n }\n output {\n stdout { }\n }\n\n $ cat pipelines.yml\n - pipeline.id: hello\n path.config: \"/opt/bitnami/logstash/config/hello.conf\"\n - pipeline.id: bye\n path.config: \"/opt/bitnami/logstash/config/bye.conf\"\n\n $ kubectl create cm multipleconfig --from-file=pipelines.yml --from-file=hello.conf --from-file=bye.conf\n ```\n\n- Deploy the Helm chart with the `enableMultiplePipelines` parameter:\n\n ```bash\n helm install logstash . --set enableMultiplePipelines=true --set existingConfiguration=multipleconfig\n ```\n\n- Create dummy events in the tracked files and check the result in the Logstash output:\n\n ```bash\n kubectl exec -ti logstash-0 -- bash -c 'echo hi >> /tmp/hello'\n kubectl exec -ti logstash-0 -- bash -c 'echo bye >> /tmp/bye'\n ```\n\n### Add extra environment variables\n\nTo add extra environment variables, use the `extraEnvVars` property.\n\n```yaml\nextraEnvVars:\n - name: ELASTICSEARCH_HOST\n value: \"x.y.z\"\n```\n\nTo add extra environment variables from an external ConfigMap or secret, use the `extraEnvVarsCM` and `extraEnvVarsSecret` properties. Note that the secret and ConfigMap should be already available in the namespace.\n\n```yaml\nextraEnvVarsSecret: logstash-secrets\nextraEnvVarsCM: logstash-configmap\n```\n\n### Set Pod affinity\n\nThis chart allows you to set custom Pod affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).\n\nAs an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.\n\n### Backup and restore\n\nTo back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-backup-restore-deployments-velero-index.html).\n\n### FIPS parameters\n\nThe FIPS parameters only have effect if you are using images from the [Bitnami Secure Images catalog](https://go-vmware.broadcom.com/contact-us).\n\nFor more information on this new support, please refer to the [FIPS Compliance section](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html).\n\n## Persistence\n\nThe [Bitnami Logstash](https://github.com/bitnami/containers/tree/main/bitnami/logstash) image stores the Logstash data at the `/bitnami/logstash/data` path of the container.\n\nPersistent Volume Claims (PVCs) are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.\n\nSee the [Parameters](#parameters) section to configure the PVC or to disable persistence.\n\n## Parameters\n\nThe following subsections list global, common, and component-specific parameters.\n\n### Global parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| `global.imageRegistry` | Global Docker image registry | `\"\"` |\n| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |\n| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `\"\"` |\n| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `\"\"` |\n| `global.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\n| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |\n| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |\n\n### Common parameters\n\n| Name | Description | Value |\n| ------------------------ | ---------------------------------------------------------------------------------------- | --------------- |\n| `kubeVersion` | Force target Kubernetes version (using Helm capabilities if not set) | `\"\"` |\n| `nameOverride` | String to partially override logstash.fullname template (will maintain the release name) | `\"\"` |\n| `fullnameOverride` | String to fully override logstash.fullname template | `\"\"` |\n| `clusterDomain` | Default Kubernetes cluster domain | `cluster.local` |\n| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |\n| `commonLabels` | Labels to add to all deployed objects | `{}` |\n| `extraDeploy` | Array of extra objects to deploy with the release (evaluated as a template). | `[]` |\n| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |\n| `diagnosticMode.command` | Command to override all containers in the deployment | `[\"sleep\"]` |\n| `diagnosticMode.args` | Args to override all containers in the deployment | `[\"infinity\"]` |\n\n### Logstash parameters\n\n| Name | Description | Value |\n| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- |\n| `image.registry` | Logstash image registry | `REGISTRY_NAME` |\n| `image.repository` | Logstash image repository | `REPOSITORY_NAME/logstash` |\n| `image.digest` | Logstash image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `image.pullPolicy` | Logstash image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |\n| `image.debug` | Specify if debug logs should be enabled | `false` |\n| `automountServiceAccountToken` | Mount Service Account token in pod | `false` |\n| `hostAliases` | Add deployment host aliases | `[]` |\n| `configFileName` | Logstash configuration file name. It must match the name of the configuration file mounted as a configmap. | `logstash.conf` |\n| `enableMonitoringAPI` | Whether to enable the Logstash Monitoring API or not Kubernetes cluster domain | `true` |\n| `monitoringAPIPort` | Logstash Monitoring API Port | `9600` |\n| `extraEnvVars` | Array containing extra env vars to configure Logstash | `[]` |\n| `extraEnvVarsSecret` | To add secrets to environment | `\"\"` |\n| `extraEnvVarsCM` | To add configmaps to environment | `\"\"` |\n| `input` | Input Plugins configuration | `\"\"` |\n| `extraInput` | Extra Input Plugins configuration | `\"\"` |\n| `filter` | Filter Plugins configuration | `\"\"` |\n| `output` | Output Plugins configuration | `\"\"` |\n| `existingConfiguration` | Name of existing ConfigMap object with the Logstash configuration (`input`, `filter`, and `output` will be ignored). | `\"\"` |\n| `extraConfigurationFiles` | Extra configuration files to be added to the configuration ConfigMap and mounted at /bitnami/logstash/config. Rendered as a template. | `{}` |\n| `enableMultiplePipelines` | Allows user to use multiple pipelines | `false` |\n| `extraVolumes` | Array to add extra volumes (evaluated as a template) | `[]` |\n| `extraVolumeMounts` | Array to add extra mounts (normally used with extraVolumes, evaluated as a template) | `[]` |\n| `serviceAccount.create` | Enable creation of ServiceAccount for Logstash pods | `true` |\n| `serviceAccount.name` | The name of the service account to use. If not set and `create` is `true`, a name is generated | `\"\"` |\n| `serviceAccount.automoun\n\n_Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-charts-logstash-index.html_","has_starred","hub_user","immutable_tags_settings",{"_110":11,"_111":112},"enabled","rules",[113],".*","is_automated","permissions",{"_117":21,"_118":11,"_119":11},"read","write","admin","user","storage_size",5532164,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_27":28,"_63":-7,"_61":-7,"_62":-7,"_29":135,"_35":36,"_137":-7,"_138":11},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":136,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/logstash:sha256-4f06f6087176d13f0ecbe8b4f859c6915cd632d36de27bda202cd144c93991fe