Skip to content

Helm Chart for Cluster API GitOps Installation / Operation #11315

Open
@tuunit

Description

@tuunit

What would you like to be added (User Story)?

As an operator of cluster API, I want to be able to install and manage Cluster API using a GitOps approach for easier deployment and management of large Kubernetes cluster environments.

Detailed Description

A Helm chart for Cluster API would provide a standardized and convenient way to deploy and manage Cluster API components. This would be particularly beneficial for GitOps workflows, where infrastructure is defined and managed declaratively as code.

Basic idea:

  • A generic Helm chart for the Cluster-API CRDs
  • Installation and upgrade of the cluster operator and webhook controller
  • On top of that, cluster-api providers could provide their own helm charts with the specific controller implementations and CRDs
  • This would allow for integration with popular GitOps tools like ArgoCD
  • Pre-configured values for common Cluster API configurations?

Anything else you would like to add?

As mentioned in issue #2811, there has been previous interest in this feature. I would be happy to contribute a PR for the Helm chart if it is deemed desirable.

Label(s) to be applied

/kind feature
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.priority/backlogHigher priority than priority/awaiting-more-evidence.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions