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

add official helm chart and repo #1306

Merged
merged 1 commit into from
Mar 30, 2022

Conversation

jackfrancis
Copy link
Contributor

What type of PR is this?

What this PR does / why we need it:

This PR introduces an official helm chart inhelm/cloud-provider-azure, as well as an official helm repo with artifacts in helm/repo (available to the world at the reference https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo).

The implementation for the components has been copied from reference resources in the repo.

Helm repo and chart validation has been added (as a new test-helm make target, which is integrated into the existing test-check target), as well as helm repo packaging scripts.

Which issue(s) this PR fixes:

Fixes #1157

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Mar 21, 2022
@coveralls
Copy link

coveralls commented Mar 21, 2022

Coverage Status

Coverage remained the same at 80.206% when pulling aa65f8d on jackfrancis:helm-chart into 807ee31 on kubernetes-sigs:master.

@jackfrancis jackfrancis force-pushed the helm-chart branch 3 times, most recently from 685e6d7 to 2d4b837 Compare March 22, 2022 17:13
- kubernetes-sigs
- kubernetes
maintainers:
- email: [email protected]
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@feiskyer @andyzhangx what do you think? I would be happy to maintain this going forward (updating with every release). Perhaps @lzhecheng can be a co-maintainer?

Also happy to add everyone who is a repo maintainer.

Copy link
Contributor

Choose a reason for hiding this comment

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

Please add me to the list. Thank you.

Copy link
Member

Choose a reason for hiding this comment

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

yes, thanks for joining as co-maintainer

@MartinForReal
Copy link
Contributor

/assign @lzhecheng

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

@lzhecheng lzhecheng left a comment

Choose a reason for hiding this comment

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

Overall lgtm. A few nits left and rebase is needed. Besides, do we need to include .tgz into the repo?

helm/cloud-provider-azure/Chart.yaml Outdated Show resolved Hide resolved
hack/verify-helm-repo.sh Show resolved Hide resolved
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 28, 2022
@jackfrancis
Copy link
Contributor Author

@lzhecheng including the actual .tgz of the chart version in the repo is how to fulfill the helm repository specification. See:

The advantage of maintaining a definitive repo is so that users are able to issue helm commands like this:

$ helm install --repo https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo cloud-provider-azure

If we don't maintain a helm repo then users will be forced to git clone the cloud-provider-repository locally, or download the helm chart in another way, which is a tedious step.

Maintaining a repo isn't entirely without effort, but I've attempted to make that effort very easy by scripting everything, and adding CI verification to ensure that future chart changes are properly versioned and published in the repo.

@lzhecheng
Copy link
Contributor

/lgtm
Thank you for the effort! @jackfrancis

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 29, 2022
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 29, 2022
@jackfrancis jackfrancis force-pushed the helm-chart branch 5 times, most recently from 5b25b13 to 116a25b Compare March 29, 2022 19:29
@jackfrancis
Copy link
Contributor Author

@lzhecheng do you have a public e-mail you're willing to include in the Chart.yaml maintainers section?

@lzhecheng
Copy link
Contributor

@lzhecheng do you have a public e-mail you're willing to include in the Chart.yaml maintainers section?

Please use [email protected]

@jackfrancis
Copy link
Contributor Author

@lzhecheng do you have a public e-mail you're willing to include in the Chart.yaml maintainers section?

Please use [email protected]

Thanks! Done.

@lzhecheng
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 30, 2022
name: cloud-node-manager
namespace: kube-system
---
apiVersion: apps/v1
Copy link
Member

Choose a reason for hiding this comment

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

could you also include the Daemonset for Windows nodes?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

I think so.

@lzhecheng
Copy link
Contributor

/hold
Let's add windows ds.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 30, 2022
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 30, 2022
command: ["/cloud-node-manager.exe"]
args:
- --node-name=$(NODE_NAME)
{{- if hasKey .Values.cloudNodeManager "cloudConfig" }}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@feiskyer @lzhecheng Windows cloud-node-manager daemonset added. Lemme know if any of the below configurable options (--cloud-config, --kube-api-burst, --kube-api-content-type, etc) are not relevant for the windows cloud-node-manager.exe runtime.

Copy link
Member

@feiskyer feiskyer left a comment

Choose a reason for hiding this comment

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

Thanks for addressing the comments

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 30, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: feiskyer, jackfrancis, lzhecheng

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

@lzhecheng
Copy link
Contributor

/lgtm
/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 30, 2022
@k8s-ci-robot k8s-ci-robot merged commit 85e09b5 into kubernetes-sigs:master Mar 30, 2022
@jackfrancis jackfrancis deleted the helm-chart branch March 30, 2022 16:03
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. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Helm chart for cloud provider
7 participants