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 V3 support #5385

Closed
wants to merge 4 commits into from
Closed

Helm V3 support #5385

wants to merge 4 commits into from

Conversation

lohmag
Copy link

@lohmag lohmag commented Nov 27, 2019

Patch to support helm3, it doesn't need tiller anymore so this part is obsolete.
Several commands also changed. Helm2 not backward compatible with 3 version.
#4777

@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
  • Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Nov 27, 2019
@k8s-ci-robot
Copy link
Contributor

Welcome @lohmag!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 27, 2019
@lohmag
Copy link
Author

lohmag commented Nov 27, 2019

/retest

@lohmag
Copy link
Author

lohmag commented Nov 27, 2019

/check-cla

@k8s-ci-robot
Copy link
Contributor

@lohmag: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@lohmag
Copy link
Author

lohmag commented Nov 27, 2019

/assign @mattymo

roles/kubernetes-apps/helm/defaults/main.yml Outdated Show resolved Hide resolved
include_tasks: "gen_helm_tiller_certs.yml"
when: tiller_enable_tls

- name: Helm | Install client on all masters
Copy link
Contributor

@mirwan mirwan Nov 27, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this task should not be removed but modified to simply add stable repo when helm_stable_repo_url is defined?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't get a point of this. If it doesn't need tiller then what for it repo in chart? I think to just delete helm_stable_repo_url in next commit

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In pre-v3, helm init not only installed tiller but also initiated the helm client on members of the kube-master group (optionally including adding stable repo). That made helm directly usable to install charts from stable repo on masters for users who chose to enable helm_stable_repo_url in their inventory.
Your changes make the current behaviour change.

@mirwan
Copy link
Contributor

mirwan commented Nov 27, 2019

/check-cla

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Nov 27, 2019
Copy link
Author

@lohmag lohmag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed odsolete vars

include_tasks: "gen_helm_tiller_certs.yml"
when: tiller_enable_tls

- name: Helm | Install client on all masters
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't get a point of this. If it doesn't need tiller then what for it repo in chart? I think to just delete helm_stable_repo_url in next commit

@mirwan
Copy link
Contributor

mirwan commented Dec 2, 2019

/lgtm /approve

@mirwan mirwan self-requested a review December 2, 2019 20:19
@Miouge1 Miouge1 added this to the 2.13 milestone Dec 4, 2019
@Miouge1
Copy link
Contributor

Miouge1 commented Dec 4, 2019

Since Helm 3 has been released every recently, I think it's too early to include that in 2.12, therefore I mark it for 2.13.

@mirwan
Copy link
Contributor

mirwan commented Dec 4, 2019

@Miouge1 Do you know why the PR has been merged despite my lgtm and approve? I guess it's because the PR may be based on an earlier commit of master than the one with me as approver, but your last comment made me doubt it...

@Miouge1
Copy link
Contributor

Miouge1 commented Dec 4, 2019

@mirwan the OWNERS file changes take effect immediately, I think it's because the commands have to be one per line.

I would prefer to hold this for 2.13 but it's up for discussion.

@mirwan
Copy link
Contributor

mirwan commented Dec 4, 2019

Is there a due date for 2.12 or is it when the related issues are done, just out of curiosity? Anyway, I'm fine with it.
Does it mean I should add a comment with lgtm approve hold (one per line) ?

@Miouge1
Copy link
Contributor

Miouge1 commented Dec 5, 2019

Yep one per line.

@mirwan
Copy link
Contributor

mirwan commented Dec 5, 2019

/lgtm
/approve

@mirwan
Copy link
Contributor

mirwan commented Dec 5, 2019

/hold

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Dec 5, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lohmag, mirwan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 5, 2019
@mirwan
Copy link
Contributor

mirwan commented Dec 5, 2019

@lohmag It seems that the support of helm v2 (as well as v3) would be a requirement until some other release so that users can migrate when they want.
It would mean to keep the removed tasks installing tiller, add condition on them (based on helm_version) and cleanup tiller pods when helm version is not v2.
I don't know if you're ok with handling this not, if not, that's fine I could modify the PR myself. Just let me know

@lohmag
Copy link
Author

lohmag commented Dec 9, 2019

@mirwan Sounds ok except for those part where it should cleanup tiller pods when helm version is not v2. It's not that easy because it need to create secrets for helm3 from helm2 tiller and etcd configs.
I found this utility to do this job -
https://github.com/helm/helm-2to3
Maybe it should be added to kubespray somehow.. I need to think more about it.

@lohmag
Copy link
Author

lohmag commented Dec 9, 2019

@mirwan I think it will be nice to add flag to config for switching beetween helm2/helm3. Helm2 will be used by default. If user has already created cluster he should migrate to helm3 by himself and switch flag.

@Miouge1
Copy link
Contributor

Miouge1 commented Dec 11, 2019

Anything I should add in the 2.12 release notes (see #5409) around Helm 2 and 3?

@lohmag
Copy link
Author

lohmag commented Dec 11, 2019

@Miouge1 Not ready yet

@Miouge1 Miouge1 mentioned this pull request Dec 12, 2019
@Miouge1
Copy link
Contributor

Miouge1 commented Dec 12, 2019

I'll copy part of the Slack discussion related to Helm v3 and how this is a bit different than #5441

maybe for 2.13, we can set helm_version to 3 by default
and for 2.14, we can remove 2 support 😉

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 12, 2019
@k8s-ci-robot
Copy link
Contributor

@lohmag: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Miouge1
Copy link
Contributor

Miouge1 commented Feb 13, 2020

Thanks everyone involved in this PR, we just merged #5503 instead.

@Miouge1 Miouge1 closed this Feb 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants