Kubeflow Helm Chart - Release Notes (v0.4.0)
Summary
Version 0.4.0
introduces new features and improvements to the Kubeflow Helm Chart, including the addition of the KServe Models Web App, replacement of the kubeflow-m2m-oidc-configurator
CronJob with a JWKS Proxy, and enhanced toggling capabilities for Kubeflow components. Additionally, the Quickstart section in these release notes has been expanded to include all available quickstart options.
Changes
-
KServe Models Web App:
- Added support for the KServe Models Web App, providing a user-friendly interface for managing deployed models within the Kubeflow environment.
-
JWKS Proxy for In-Cluster OIDC Issuer:
- Replaced the
kubeflow-m2m-oidc-configurator
CronJob with a JWKS Proxy for handling self-signed in-cluster OIDC Issuers. - Important: The JWKS Proxy is intended only for Kubernetes clusters that use self-signed in-cluster OIDC Issuers, such as default deployments with Kind, vCluster, Minikube, and similar environments. It is not required for clusters that use publicly trusted certificates for the in-cluster OIDC provider, such as AWS EKS or GCP GKE.
- Replaced the
-
Improved Enable/Disable Toggles for Components:
- Enhanced the toggling capabilities of individual Kubeflow components, allowing finer control over which features are enabled or disabled during deployment.
Quickstart
The Quickstart section in these release notes has been expanded to cover all available deployment options for the Kubeflow Helm Chart. Follow the instructions below to quickly set up Kubeflow on your preferred platform.
All of the quickstarts (except for the quickstart.helm.eks.sh) are configured for local testing in clusters deployed with kind, vcluster or minikube. For reference on what values need to be provided for clusters deployed on AWS EKS, GCP GKE or similar, please refer to the quickstart.helm.eks.sh
.
Detailed instructions are available in each of the quickstart scripts.
Local Deployment with plain Helm
For local testing and development, you can use quickstart.helm.local.sh
to deploy the Kubeflow Helm Chart.
Use this script for development. It will use the values from your local git repository configured under example/helm
directory.
Please remember this script assumes you're running K8s Cluster with self-signed OIDC Issuer (kind, vcluster, minikube).
$ git clone https://github.com/kromanow94/kubeflow-manifests.git
$ cd kubeflow-manifests/example/helm
$ ./quickstart.helm.local.sh
Remote deployment with plain Helm
If you don't want to clone this repository and just want to have a quick check if the Kubeflow installation works OOB in your cluster, use this script.
Please remember this script assumes you're running K8s Cluster with self-signed OIDC Issuer (kind, vcluster, minikube).
$ curl https://raw.githubusercontent.com/kromanow94/kubeflow-manifests/refs/tags/kubeflow-0.4.0/example/helm/quickstart.helm.sh | bash
Deployment with ArgoCD
Install and configure ArgoCD to manage Kubeflow and its dependencies.
Please remember these scripts assumes you're running K8s Cluster with self-signed OIDC Issuer (kind, vcluster, minikube).
Basic ArgoCD Setup
Installs ArgoCD (if not already installed) and applies separate ArgoCD Apps for dependencies and the Kubeflow Helm Chart.
$ curl -s https://raw.githubusercontent.com/kromanow94/kubeflow-manifests/refs/tags/kubeflow-0.4.0/example/helm/quickstart.argocd.sh | bash
App of Apps with ArgoCD
Installs and configures ArgoCD with health assessments and deploys the App of Apps manifest for Kubeflow and its dependencies.
$ curl -s https://raw.githubusercontent.com/kromanow94/kubeflow-manifests/refs/tags/kubeflow-0.4.0/example/helm/quickstart.app-of-apps.sh | bash
Deployment on AWS EKS
For production-grade deployments on AWS EKS, use the provided reference script:
$ git clone https://github.com/kromanow94/kubeflow-manifests.git
$ cd kubeflow-manifests/example/helm
$ ./quickstart.helm.eks.sh
Note: The EKS script is for reference only and requires customization based on your specific setup.