Skip to content
This repository was archived by the owner on Nov 1, 2022. It is now read-only.

Latest commit

 

History

History
77 lines (57 loc) · 2.85 KB

using-yamls.md

File metadata and controls

77 lines (57 loc) · 2.85 KB

Get started using YAMLs

🛑 Upgrade Advisory

This documentation is for Helm Operator (v1) which has reached its end-of-life in November 2022.

We strongly recommend you familiarise yourself with the newest Flux and migrate as soon as possible.

For documentation regarding the latest Flux, please refer to this section.

This guide walks you through setting up the Helm Operator using deployment YAMLs.

Prerequisites

  • Kubernetes cluster >=1.1.3.0
  • kubectl
  • (Optional) Tiller (secure setup)

Install the Helm Operator

First, install the HelmRelease Custom Resource Definition. By adding this CRD it will be possible to define HelmRelease resources on the cluster:

kubectl apply -f https://raw.githubusercontent.com/fluxcd/helm-operator/1.4.4/deploy/crds.yaml

Proceed to create the flux namespace, this is the namespace the Helm Operator will be deployed to:

kubectl create namespace flux

Apply the ServiceAccount, ClusterRole and ClusterRoleBinding so that the Helm Operator can access cluster resources:

kubectl apply -f https://raw.githubusercontent.com/fluxcd/helm-operator/1.4.4/deploy/rbac.yaml

Apply the Helm Operator deployment itself:

kubectl deploy -f https://raw.githubusercontent.com/fluxcd/helm-operator/1.4.4/deploy/deployment.yaml

Helm 3

The default deployment of the Helm Operator comes with support for Helm 2 and 3 enabled. To disable support for Helm 2 (and recover from the Tiller connection failure), patch the resource to set --enabled-helm-versions=v3:

kubectl deploy -f https://raw.githubusercontent.com/fluxcd/helm-operator/1.4.4/deploy/deployment.yaml \
    --type='json' \
    -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value":"--enabled-helm-versions=v3"}]'

Helm 2

The default deployment of the Helm Operator does enable support for Helm 2 but does not take any custom configurations like Tiller TLS settings into account. If your Tiller is e.g. in a different namespace than kube-system or securely setup, take a look at the available Tiller configuration flags and commented out sections in the example deployment to further tweak your Helm Operator installation.

Next