Additional Maintainer Needed

[Vad1mo]

We would like to bring this Helm chart to the next level, in terms of automation, governance and documentation. This can only be achieved with a diverse community. Hence, we are looking for additional maintainers and contributors to join this project. Respond here if you're interested in helping this project reach the next level.

---

Update 16 July 2025

We have quite a few open PRs that would need to have a review and testing and making sure they align with the guidelines, documentation etc...

• https://github.com/8gears/n8n-helm-chart/pulls
• https://github.com/8gears/n8n-helm-chart?tab=readme-ov-file#contribution-guide

[TartanLeGrand]

Hi, I'm really interested in taking this repo/chart to the next level! 🔥

Can't wait to share my devops knowledge and automate a few more things and improve the chart. 🚀

[Vad1mo]

happy to have you onboard. I think this owuld be the task we urgently need
#27

[x-504]

Hi guys, we are currently using this helm-chart and would be more than happy to contribute.

Let me know!

[sush0408]

I have also used n8n in my k8s setup. Will be happy to contribute.

Thanks

[RoseSecurity]

@Vad1mo Would love to assist with this chart. Is there an established pattern for updating the chart version?

[Vad1mo]

Now there is indeed a workflow, at least for the release workflow.

https://github.com/8gears/n8n-helm-chart/blob/main/README.md#chart-release-workflow

[awdemos]

Hi! I just discovered the chart and would be interested in contributing. If it is possible I could suggest a Discord channel to organize communication. I'm a Senior DevOps Engineer and I work in an AI CoE that is going to start using n8n on Kubernetes.

[dadangnh]

Hi, I'm happy to help maintain the chart. Please review my first contribution in this PR

[Vad1mo]

This chart is currently redesigned to better support the changed config option of n8n. Please follow the issue #129 for more details and the current state of development. It should be ready in January 2025.

Currently, it makes no sense to accept PRs,

[jcconnects]

I would be happy to help maintain this chart!

[MohamedOmari-Devops]

Hello, i am would be happy to help to.

[Vad1mo]

Thank your offer:

We have quite a few open PRs that would need to have a review and testing and making sure they align with the guidelines, documentation etc...

https://github.com/8gears/n8n-helm-chart/pulls
https://github.com/8gears/n8n-helm-chart?tab=readme-ov-file#contribution-guide

[dsmello]

Hello @Vad1mo , I can try to help. At least to solve minor bugs and review some PR's too.

[yuriolisa]

I'd be glad to help!!

[joshuabaird]

@Vad1mo How can we help? I think there are several PR's which need reviewed and merged. Thanks!

[cgn170]

Hello @Vad1mo , I'd be happy to help

[Vad1mo]

I can need some help on that chart. Best help is to test the PRs, make sure there are no side effects or breaking changes. Readme is up to date, maybe this new feature needs its own example? Values.yaml is correct.

Then it is easy for me to merge that in

[babu97]

Hello do you still require new maintainers ?
I recently deployed N8N to my cluster and would like to contribute a lot

[Vad1mo]

yes, the project needs people how can review and test PRs

[cjbarroso]

Hi, I'm using this chart in my business and eager to contribute to speed up things.

[mjrgr]

Hi!
I can contribute to the project too if any help is needed 😜

[Vad1mo]

the main problem is that most of the PRs are broken, not code wise but pipeline wise.Mostly no one is following https://github.com/8gears/n8n-helm-chart/blob/main/CONTRIBUTING.md

[Vad1mo]

To be clear I/we are not interest to be the sole owner of this repo, however we are very much interested in this chart to be stable and backwards compatible. the best thing you can do as contributor/maintainer is to make sure the PRs are tested, documented and correct and are backward compatible.