Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Working together on a helm chart #415

Closed
EugenMayer opened this issue Jan 4, 2024 · 2 comments
Closed

[Feature Request]: Working together on a helm chart #415

EugenMayer opened this issue Jan 4, 2024 · 2 comments
Labels
enhancement It's not a bug, but it's worth an enhancement.

Comments

@EugenMayer
Copy link
Contributor

Description / Beschreibung

Hey there,

visiting https://docs.buanet.de/iobroker-docker-image/docs/ due to my interest in running ioBroker in a container env. i stumbeled uppon the guy with the role "Smarthome on docker" :)

I'am currently build out my homelab, switched from plain containerd/podman+docker-compose to k8s entirely. Next step is to run ioBroker in k8s and AFAICS, there is no helm chart yet, so i'am going to make one most probably.

That in mind, i asked myself if you are interested in working together on this adventure - my goals are

  • ensure one can run with out-discovery and utilizing VLAN based networking (home automation network isolation) - this is what i plan to use multus for
  • ensure to run ioBroker as slim as possible, keep services like redis and other things in seperate pods/containers (scaling)
  • scaling via multimode - since i have a 1+ node cluster anyway, this helps spreading the load (which ioBroker can be very good at creating :) )
  • i would avoid containerizing ioBroker myself is possibel , this is where this project might be interesting to use with

The last point might need a bit of adoption (more or less introducing ENV vars if any - but there is a lot here already, so might not be needed at all).

What are your thoughts about all of this?

Thanks for this little gem of a project :)

@EugenMayer EugenMayer added the enhancement It's not a bug, but it's worth an enhancement. label Jan 4, 2024
@EugenMayer
Copy link
Contributor Author

Created a first (working) draft here https://github.com/EugenMayer/helm-charts/tree/task/iobroker/charts/iobroker

Taken care of:

  • env based config
  • volume / persistence
  • ingress

TODO:

  • networking (multicast/broadcast) VLAN support via multus as an option

@buanet
Copy link
Owner

buanet commented Jan 4, 2024

If I take a look into the ioBroker community, I only see a very very small target group for running ioBroker inside a kubernetes cluster... So, for me, there is no need to put time into this to make something like a helm-chart available to the community.

As I'm not able to put more time into this project, I will only focus to things with bigger target groups in the community.
That doesn't say, that I won't support your effort.

I'll convert this issue to an discussion. So if there is somebody out there waiting for a helm-chart her/ she can easily join you.

Regards,
André

Repository owner locked and limited conversation to collaborators Jan 4, 2024
@buanet buanet converted this issue into discussion #417 Jan 4, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement It's not a bug, but it's worth an enhancement.
Projects
None yet
Development

No branches or pull requests

2 participants