Graylog Helm Chart for Kubernetes: Beta V.1.0.0 Now Available
Running Graylog on Kubernetes has been possible for a while, but let’s be honest: it usually involved a fair amount of DIY. Custom manifests, duct-taped values files, and more than one late-night kubectl describe pod.
That changes today.
We’re releasing the first-ever Graylog Helm chart for Kubernetes — now available in beta. This chart provides teams with a cleaner, more repeatable way to deploy Graylog in Kubernetes using familiar Helm workflows, while maintaining flexibility firmly in your hands.
If you’ve been waiting for an easier on-ramp to running Graylog in K8s, this is for you.
Why a Helm Chart and Why Now?
Kubernetes is table stakes for many teams running modern infrastructure. Helm has become the standard way to manage application deployments without turning every change into a bespoke engineering project.
With this beta release, we wanted to:
- Reduce friction for Kubernetes-based Graylog installs
- Provide sane defaults without hiding important knobs
- Make deployments more repeatable across environments
- Lay the groundwork for tighter Kubernetes-native operations going forward
This chart is intentionally focused. It doesn’t try to solve every possible architecture or opinionated setup. Instead, it provides a solid, transparent starting point that you can adapt to your specific environment.
What the Helm Chart Includes
At a high level, the Graylog Helm chart helps you deploy:
- The Graylog application
- Graylog Data Node for log storage
- MongoDB Operator Chart
- Kubernetes-native configuration via values files
- Standard Helm lifecycle management (install, upgrade, rollback)
- Includes scaling nodes up and down in your deployment
You get a deployment that fits naturally into existing Helm-based workflows — CI pipelines, GitOps tooling, and environment-specific overrides all work the way you’d expect.
No magic. No surprises.
What “Beta” Means Here
This is a first-time release, and we’re using the term ‘beta’ intentionally.
That means:
- The chart is functional and usable today
- APIs and values may change based on feedback
- We expect real-world input from Kubernetes users
- Documentation will continue to evolve alongside the chart
If you’ve deployed Graylog in Kubernetes before, you’ll likely recognize the components — but now they’re packaged in a way that’s easier to reason about, version, and maintain.
Who Should Try this Now?
This beta is a good fit if you:
- Want to run Kubernetes in testing and development
- Prefer Helm over handcrafted manifests
- Want a cleaner way to deploy Graylog in K8s
- Are comfortable providing feedback or opening issues on GitHub
If you’re looking for a fully turn-key, click-button experience, this release probably isn’t aimed at you yet. This one is for builders.
Documentation and Next Steps
All installation steps, configuration options, and examples are available on GitHub, alongside the chart itself. That’s the source of truth, and it’s where updates will land first.
- Head to the Graylog GitHub repo to get started, review the requirements docs, and try the Helm chart
- Found something unclear or missing? Open an issue — we’re actively listening
This beta is the first step toward making Graylog feel at home in Kubernetes environments. Your feedback will directly shape what comes next.
What’s Coming Next
We’re starting simple and building deliberately. Based on feedback, future iterations may include:
- Expanded configuration examples
- More deployment patterns
- Clearer upgrade paths
- Tighter alignment with common Kubernetes operational models
But first, we want to see how you use it.
If you’re running Graylog on Kubernetes — or planning to — we’d love for you to take the Helm chart for a spin and tell us what works, what doesn’t, and what you’d like to see next.
