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

Remove Helm #224

Closed
laisbsc opened this issue Jan 4, 2021 · 7 comments
Closed

Remove Helm #224

laisbsc opened this issue Jan 4, 2021 · 7 comments
Labels
status: stale 🥖 Not up to date with the default branch - needs update type: enhancement 💅🏼 New feature or request

Comments

@laisbsc
Copy link
Contributor

laisbsc commented Jan 4, 2021

We would like to gradually remove Helm from QHub's dependencies.

  • Why is it necessary?
    Because Helm has created several issues, such as the one on discussion #218.

  • How will we do this?
    The team suggested Sprints as modus operandi since it is a laborious task.


Implication

Once the Helm dependency is removed we will be able to Upgrade Dask Gateway #62 #215

@laisbsc laisbsc added the Epic label Jan 4, 2021
@laisbsc
Copy link
Contributor Author

laisbsc commented Jan 4, 2021

This is the epic to track the issue on Helm's removal from QHub. Please feel free to add any details.

Once we have the initial sprint meeting, we can start creating issues to link to this epic.

@tylerpotts how does that sound?

@tylerpotts
Copy link
Contributor

We created a chart showing the current plan for the infrastructure without Helm. We have yet to create issues, but will do that as we spend more time on this

Removing Helm QHub

@laisbsc laisbsc added this to In progress in QHub Board Roadmap Jan 6, 2021
@laisbsc laisbsc moved this from In progress to To do in QHub Board Roadmap Jan 7, 2021
@verhulstm
Copy link

what "deployment pattern" do you want to use instead of helm?

@costrouc
Copy link
Member

@verhulstm right now we have three template languages in use on qhub:

  • cookiecutter(jinja2)
  • terraform
  • helm

Having these three layers has made it really difficult to onboard people for new development and helping them know where to contribute. Terraform has a kubernetes provider https://github.com/hashicorp/terraform-provider-kubernetes-alpha which has support for crds and required kubernetes version >= 1.18. We're really trying to remove as many layers of abstraction as possible ... that said I'm not a huge fan of terraform kubernetes syntax and translating the charts.

Most importantly I've found helm charts are often opinionated and dont provide features that we need the two that come to mind are dask-gateway and the zero to jupyterhub helm charts.

@laisbsc laisbsc added this to the Remove Helm milestone Jan 25, 2021
@laisbsc laisbsc removed this from To do in QHub Board Roadmap Jan 25, 2021
@costrouc
Copy link
Member

costrouc commented Feb 9, 2021

To break this into pieces that need to be done:

  • jupyterhub
  • ingress
  • dask-gateway

@laisbsc laisbsc removed this from the Remove Helm milestone Mar 11, 2021
@github-actions
Copy link

github-actions bot commented Jun 1, 2021

This issue has been automatically marked as stale because there was no recent activity in 60 days. Remove the stale label or add a comment, otherwise, this issue will automatically be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the status: stale 🥖 Not up to date with the default branch - needs update label Jun 1, 2021
@github-actions
Copy link

github-actions bot commented Jun 9, 2021

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as completed Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: stale 🥖 Not up to date with the default branch - needs update type: enhancement 💅🏼 New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants