feat(chart): add Helm chart for Kubeflow Pipelines

[tehmas]

Description of your changes:

This pull request introduces a new Helm chart for deploying Kubeflow Pipelines v2.15.0 in Kubernetes Native API Mode. It adds all the necessary Kubernetes manifests, including CRDs, RBAC, deployments, services, and configuration for the core pipeline components, with a particular focus on cache and cache deployer functionality. The chart is designed to work with or without cert-manager and supports configuration via Helm values.

The most important changes are:

Helm Chart Structure and Configuration:

• Introduced a new Helm chart (Chart.yaml) for Kubeflow Pipelines v2.15.0, including metadata, versioning, and prerequisites for Kubernetes Native API Mode.
• Added _helpers.tpl with reusable Helm template helpers for naming, labels, service accounts, namespaces, and config checksums to standardize resource generation.

Custom Resource Definitions (CRDs):

• Added CRDs for Pipeline, PipelineVersion, ScheduledWorkflow, and Viewer to support Kubernetes-native management of pipelines and related resources.

Cache and Cache Deployer Components:

• Implemented manifests for the cache server and cache deployer, including deployments, services, service accounts, roles, and role bindings, with conditional logic for enabling/disabling components and cert-manager integration. [1] [2] [3]

RBAC and Cluster Permissions:

• Added cluster-wide RBAC resources for the cache deployer, including ClusterRole and ClusterRoleBinding for certificate and webhook management when cert-manager is not used.

Centralized Configuration:

• Added a ConfigMap (pipeline-install-config) to centralize configuration for the deployment, including database settings, cache parameters, storage, and operational flags, with instructions for safe updates.

Checklist:

• You have signed off your commits
• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[github-actions]

🎉 Welcome to the Kubeflow Pipelines repo! 🎉

Thanks for opening your first PR! We're excited to have you onboard 🚀

Next steps:

• Check out the Contributing Guide for repo-specific guidelines and the Kubeflow Contributor Guide for general community standards
• Join our #kubeflow-pipelines Slack channel
• Attend the Kubeflow Pipelines WG meetings

Feel free to ask questions in the comments.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mprahl for approval. For more information see the Kubernetes Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[google-oss-prow]

Hi @tehmas. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[juliusvonkohout]

Please check first the effort and comments here: kubeflow/manifests#3237 especially the topic about standardization and consolidation with the other helm charts there and only exposing what could be really useful and sensible as platform administrator.

[juliusvonkohout]

I see multiple ones. 1. the general one kubeflow/community#832 2. KFP specific ones #12842 #12787 #12723

and some requirements from GSOC https://www.kubeflow.org/events/upcoming-events/gsoc-2026/#project-5-helm-charts

"
Details: This project continues the KSC-approved initiative to provide Kubeflow platform and standalone components via Helm. The goal is to move beyond Kustomize-only deployments to offer minimalistic, maintainable Helm charts that reflect Kustomize defaults 1:1. Key tasks include: developing and testing Helm charts for KFP and Katib, implementing CI/CD testing infrastructure for Helm-based deployments and coordinating with component maintainers to ensure cross-project consistency.

This project will touch most components and continue the helm chart initiative started by Kunal Dugar who also helped a lot with the testing infrastructure. This will therefore also include working with maintainers of other components such as KFP maintainersfor the KFP helm charts, security and scalability topic or Katib maintainers for Katib helm charts. Some have already open PRs and there was a formal vote by the KSC (Kubeflow steering Committee) that we are moving forward with offering Kubeflow platform and standalone components as helm charts. Therefore it is not just the technical part, but also the coordination effort. The goal is to make minimalistic helm charts that are easy to maintain next to kustomize and only expose sensible settings relevant to most users. For the time being the rendered chart default values must replicate kustomize 1:1. The testing infrastructure has already been set up in the GSOC 2025 efforts in kubeflow/manifests where we already have a few helm charts.
"