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 chart for cloud provider #1157

Closed
CecileRobertMichon opened this issue Feb 17, 2022 · 0 comments · Fixed by #1306
Closed

Helm chart for cloud provider #1157

CecileRobertMichon opened this issue Feb 17, 2022 · 0 comments · Fixed by #1306
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@CecileRobertMichon
Copy link
Contributor

CecileRobertMichon commented Feb 17, 2022

What would you like to be added:

A Helm chart for installing CCM and CNM. Example of another project doing something similar: https://github.com/cilium/cilium/tree/v1.11.1/install/kubernetes/cilium

Why is this needed:

Now that external cloud provider is becoming the default in future versions of Kubernetes, we need to provide users an easy way to install and upgrade their cloud provider components. Because there is such a strict dependency between cloud provider version and Kubernetes version (see version matrix in https://github.com/kubernetes-sigs/cloud-provider-azure#current-status), this requires users to manually check that their version of Kubernetes is compatible with their version of cloud-provider. A Helm chart would allow us to benefit from the kubeVersion field to define k8s version constraints instead having to deal with those manually. It would also make upgrading the version of cloud provider along with k8s version easier and make sure cloud provider users aren't running old versions in their clusters, making them less likely to run into bugs.

@CecileRobertMichon CecileRobertMichon added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 17, 2022
@nilo19 nilo19 added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants