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

Integrate Helm 3 in Rancher #20596

Open
ankur111 opened this issue May 31, 2019 · 3 comments

Comments

@ankur111
Copy link

commented May 31, 2019

No description provided.

@pietervogelaar

This comment has been minimized.

Copy link

commented Sep 11, 2019

Is it already possible to use Helm 3 beta with Rancher somehow?

@pietervogelaar

This comment has been minimized.

Copy link

commented Sep 11, 2019

Because of helm/helm#2060 Helm 2 is a deal breaker for us. It's one of the things they solved https://v3.helm.sh/docs/faq/. The latest version is now Helm 3 beta 3.

@pietervogelaar

This comment has been minimized.

Copy link

commented Sep 11, 2019

I can confirm that Helm v3.0.0-beta.3 is usable with Rancher v2.2.8. Helm 3 has Tiller completely removed, so the chart is rendered locally by the helm command. Only the helm command and a Chart repository are required.

I have a custom Chart repository setup with ChartMuseum. It contains a chart called "generic-app".

On my laptop I have the command helm (v3.0.0-beta.3) and with export KUBECONFIG=.... I point to the kubeconfig file I downloaded from the Rancher UI for my cluster.

helm upgrade example-ruby-api generic-app --install --version 0.1.0 --repo http://localhost:8080 --namespace development-early-adopters --set image.tag=latest
helm upgrade example-ruby-api generic-app --install --version 0.1.0 --repo http://localhost:8080 --namespace development-late-majority --set image.tag=stable

This installs the Chart correctly into the proper namespace. Because of helm 3, the same release name can exist in different namespaces.

All the native Kubernetes resources like deployments, services etc. are visible in the Rancher UI.

The "App" page however is (off course) still empty. Helm 3 releases are now stored in-cluster as secrets in the same namespace as specified with the --namespace parameter during helm install or helm upgrade. So this App page will have to query them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.