-
Notifications
You must be signed in to change notification settings - Fork 173
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
Helmsman roadmap #321
Comments
I really like the idea of drawing a map for the product. While Helm v3 will change drastically the way helm works, since we have helm-tiller on the board, the changes will mainly focus on removing redundant tiller-aware part of code. I've started working on it, but some more important things came up and had to stop my work. |
I'd also go through all the issues still open and close most of the ones being inactive or not confirmed to get broader view of current state |
Looks good to me, only one concern about enforcing the GitOps model, my current use case for Helmsman is no GitOps. I have a controller that manages a desired state CRD and generates k8s jobs that run Helmsman to apply the state, one desired state per namespace. And I use the tillerless mode for this. |
I was going to work on some cleaning and refactoring but if you're already working on helmv3 it might conflict. My plan was to convert some of the functions into object methods of the release and desired state objects and maybe group some of the code into packages. |
@sami-alajrami I'll need some help with preparing CI for helm 3. Maybe even an access for me to circleci and other places that would help do that? |
@sami-alajrami great to see the momentum going on that .. I am not sure I can sort the circleci access since it's tied to Github organization. |
@sami-alajrami yes, the bare minimum would be unblocking the CI parts for helm v3 with proper test image to run tests against helm 3. We can’t afford missing this sweet spot where people are starting to choose their deployment manager for helm 3 :-) |
Sounds good to me .. I think you can do the branch changing whenever you feel the helm 3 is taking shape (perhaps do it right away - create a helmsman 1.x branch from master and push it, then merge your PR when it's ready) and we carry on development from there on master. |
Thank you for engagement. I think we can try out the image from test files from branch holding the v3, it has just updated helm to 3 and one plugin, no additional changes were needed |
|
great, finally got tests passing for the first time :-) |
@sami-alajrami build on dockerhub for newest commit (which is merge of helm-v3 branch) has failed and I can't even see what was wrong. Will you help please sort it out? :-) |
it was a temporary glitch in CircleCI , a reRun without changes has worked fine. |
Absolutely loving this. I've been looking into different ways of doing ephemeral clusters for local development in a distributed architecture. Tested out armador, but eg. the lack of branch support makes me hesitant. |
Any chance to consider loading non Helm manifests? For example if some service has a url and all you have to do is |
This issue has been marked stale due to an inactivity. |
@luisdavim @mkubaczyk (and others), I have drafted a document outlining a potential roadmap for improvements and new features in Helmsman as it moves to support helm v3.
https://docs.google.com/document/d/1tpOnR_DvVUczJQFnnY9FCAYaFn55PqWURmNFdzh-pHk/edit?usp=sharing
I would love your feedback and input on this and we might schedule a hangout to finalize it and break it down into backlog tasks and milestones.
The aim is to help guide community contributions towards a common goal.
The text was updated successfully, but these errors were encountered: