HelmRepository and HelmRelease kinds.
With Flux, Timoni users can take full advantage of existing Helm charts.
Timoni Bundles can refer to Helm charts hosted on Helm HTTPS and OCI repositories,
and supports setting Helm release values in the same way you would do for Timoni instances.
Install Flux helm-controller
Install Flux helm-controller on a Kubernetes cluster with:Deploy Helm charts
To deploy Helm charts on clusters with Flux installed, you’ll be using the flux-helm-release Timoni module. This module generates FluxHelmRepository and HelmRelease objects and allows
the configuration of the Helm repository HTTP/S or OCI URL, auth token, chart name, and Helm release values.
Public repositories
Example of deployingcert-manager and ingress-nginx Helm charts to a Kubernetes cluster:
cert-manager release, then will proceed with the ingress-nginx installation.
After the releases are installed, Flux will scan for new chart versions every hour,
and will upgrade a release if a new chart version is found. To disable the automated
upgrade, you can set a fix version for each chart under values: chart: version.
Private repositories
When using Helm charts from a private Helm HTTPS or OCI repository, you can provide the auth credentials in the Bundle using Timoni runtime attributes. Example of deploying thepodinfo Helm chart from GitHub Container Registry
using a GitHub PAT for auth:
GITHUB_TOKEN is set in your environment, apply the bundle
using the --runtime-from-env flag and Timoni will fill in the token value: