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

Introduce helm component #522

Closed
bryanl opened this Issue May 8, 2018 · 6 comments

Comments

Projects
2 participants
@bryanl
Member

bryanl commented May 8, 2018

ksonnet should be able to consume helm charts as a component type.

Helm Registry

  • ksonnet will expose Helm repositories as registries
  • Helm based registries can expose their contents as prototypes #664
  • Helm registries can manage multiple Chart releases simultaneously. #672
  • Helm registry should attempt to cache entries

Notes

Helm upgrade

A ksonnet user should be able to upgrade a chart to the specific version or the latest release.

@bryanl bryanl added the feature label May 8, 2018

@bryanl bryanl added this to the 0.11.0 milestone May 18, 2018

@bryanl bryanl modified the milestones: 0.11.0, 0.12.0 May 25, 2018

@bryanl bryanl referenced this issue May 25, 2018

Closed

ksonnet 0.12 sprint #562

4 of 4 tasks complete
@burdiyan

This comment has been minimized.

burdiyan commented May 28, 2018

One thing to take into account that is specific to Helm is hooks: https://github.com/kubernetes/helm/blob/master/docs/charts_hooks.md

I think that replicating this functionality should not be a goal, so maybe Ksonnet should interact with Tiller to install Helm charts, instead of rendering them locally.

@bryanl

This comment has been minimized.

Member

bryanl commented May 28, 2018

I'm actually leaning towards making helm charts registries and using the helm rendering engine to generate something ksonnet can understand. The goal for this is not to replicate all of helm inside of ksonnet, but to instead make charts (and their dependencies) available to ksonnet.

@burdiyan

This comment has been minimized.

burdiyan commented May 28, 2018

Some Charts inside stable Helm repository are using hooks as a crucial part of the chart. For example mongodb-replicaset chart is using post-install hook to form the actual ReplicaSet after all nodes are up.

@bryanl

This comment has been minimized.

Member

bryanl commented Jun 1, 2018

@burdiyan after reviewing the hooks, the first version of this feature will not include support for hooks. ksonnet's operating model is declarative and hooks are imperative, so this fit is not obvious.

@burdiyan

This comment has been minimized.

burdiyan commented Jun 4, 2018

@bryanl Make sense for the initial implementation. Although would be great if ksonnet fail when trying to import a chart with hooks. Or at least a warning.

@bryanl

This comment has been minimized.

Member

bryanl commented Jun 4, 2018

@burdiyan that is the plan. Working out when and where to fail right now.

@bryanl bryanl self-assigned this Jun 12, 2018

@shomron shomron added this to In progress in Milestone 0.12.0 Jul 2, 2018

@bryanl bryanl closed this Jul 4, 2018

Milestone 0.12.0 automation moved this from In progress to Done Jul 4, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment