Skip to content
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

Helm Chart #112

Open
maheckathorn opened this issue Aug 14, 2024 · 9 comments
Open

Helm Chart #112

maheckathorn opened this issue Aug 14, 2024 · 9 comments
Assignees
Labels
enhancement New feature or request

Comments

@maheckathorn
Copy link

Hello,

Would a helm chart be a feature that the MISP project is interested in? If so, would this repo be the appropriate place for that feature or would a different or even new MISP Helm repo be more appropriate?

Helm does offer a good deployment method for running MISP on production workloads. The main project has some discussion about personal Helm charts, but nothing about an officially supported option.

@ostefano
Copy link
Collaborator

Yep definitely.

Let's start with a PR with this project and we can't take it from there.

@ostefano ostefano added the enhancement New feature or request label Aug 24, 2024
@hodgigre
Copy link

Hello both. I'm just curious if you made any inroads on this front? On a related note I wonder whether these issue here has been resolved? Support: Split frontend/background workers · Issue #8616 · MISP/MISP (github.com) Thanks so much.

@ostefano
Copy link
Collaborator

Re first question you got to ask @maheckathorn , re second question you got to ask @iglocska

@maheckathorn
Copy link
Author

We have working code that we are making use of internally. However, our process for open sourcing work is time consuming. I'm not going to be able to give a time line at this point.

@hodgigre
Copy link

Thank you for the update @maheckathorn. Are you using MISP on K8S in production? Has said architecture met your goals/objectives - any significant concerns or gaps? Would you recommend pursuit of this over native VM installs and related auto scaling technologies. We're actually targeting GKE. Thanks again.

@maheckathorn
Copy link
Author

We're proving out making use of it in production. It's been working well. One of the benefits of using k8s over other scaling tech or native VM installs is access to the full k8s ecosystem. This allows us to use things like flux or ArgoCD for doing Continuous deployment via GitOPs, for one example. On cloud providers, we have also proved out swapping in database as a service offerings for the DB backend and that has been seamless.

@ostefano
Copy link
Collaborator

@maheckathorn this is becoming more and more desirable/critical.
Is there anything we can do on the MISP side to facilitate this?

@maheckathorn
Copy link
Author

Not really, the ball is currently in our corner and we are beginning the legal conversations required to allow us to proceed to open sourcing our work.

@AxFrancois
Copy link

A helm chart would be very useful. I hope you can get over the administrative and legal burden soon👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants