Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration, and automating updates to configuration when there is new code to deploy.

Last update: Jan 8, 2023

Overview

Flux version 2

Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories), and automating updates to configuration when there is new code to deploy.

Flux version 2 ("v2") is built from the ground up to use Kubernetes' API extension system, and to integrate with Prometheus and other core components of the Kubernetes ecosystem. In version 2, Flux supports multi-tenancy and support for syncing an arbitrary number of Git repositories, among other long-requested features.

Flux v2 is constructed with the GitOps Toolkit, a set of composable APIs and specialized tools for building Continuous Delivery on top of Kubernetes.

Flux installation

With Homebrew for macOS and Linux:

brew install fluxcd/tap/flux

With GoFish for Windows, macOS and Linux:

gofish install flux

With Bash for macOS and Linux:

curl -s https://fluxcd.io/install.sh | sudo bash

# enable completions in ~/.bash_profile
. <(flux completion bash)

Arch Linux (AUR) packages:

flux-bin: install the latest stable version using a pre-build binary (recommended)
flux-go: build the latest stable version from source code
flux-scm: build the latest (unstable) version from source code from our git main branch

Binaries for macOS AMD64/ARM64, Linux AMD64/ARM/ARM64 and Windows are available to download on the release page.

A multi-arch container image with kubectl and flux is available on Docker Hub and GitHub:

docker.io/fluxcd/flux-cli:
ghcr.io/fluxcd/flux-cli:

Verify that your cluster satisfies the prerequisites with:

flux check --pre

Get started

To get started with Flux, start browsing the documentation or get started with one of the following guides:

If you need help, please refer to our Support page.

GitOps Toolkit

The GitOps Toolkit is the set of APIs and controllers that make up the runtime for Flux v2. The APIs comprise Kubernetes custom resources, which can be created and updated by a cluster user, or by other automation tooling.

You can use the toolkit to extend Flux, or to build your own systems for continuous delivery -- see the developer guides.

Components

Community

Need help or want to contribute? Please see the links below. The Flux project is always looking for new contributors and there are a multitude of ways to get involved.

Getting Started?
- Look at our Get Started guide and give us feedback
Need help?
- First: Ask questions on our GH Discussions page
- Second: Talk to us in the #flux channel on CNCF Slack
- Please follow our Support Guidelines (in short: be nice, be respectful of volunteers' time, understand that maintainers and contributors cannot respond to all DMs, and keep discussions in the public #flux channel as much as possible).
Have feature proposals or want to contribute?
- Propose features on our GH Discussions page
- Join our upcoming dev meetings (meeting access and agenda)
- Join the flux-dev mailing list.
- Check out how to contribute to the project

Events

Check out our events calendar, both with upcoming talks, events and meetings you can attend. Or view the resources section with past events videos you can watch.

We look forward to seeing you with us!

Comments

AKS: Azure network policy addon blocks source-controller ingress
Dears,

I'm trying to bootstrap flux2 in a new azure AKS without any network policies defined. After all CRDs are installed and the GitHub account is create, the bootstrap finishes with (time exceeded). The four controller pods are up and running.

The cluster is synchronized with the last commit correctly as below:

#kubectl get gitrepositories.source.toolkit.fluxcd.io -A NAMESPACE NAME URL READY STATUS AGE flux-system flux-system https://github.com/name/tanyflux True Fetched revision: main/6554ea6324d70caf0f2dfa200e137fd9c2aecc8a 59m

But the Kustomization has the below error : #kubectl get kustomizations.kustomize.toolkit.fluxcd -A failed to download artifact from http://source-controller.flux-system.svc.cluster.local./gitrepository/flux-system/flux-system/6554ea6324d70caf0f2dfa200e137fd9c2aecc8a.tar.gz, error: Get "http://source-controller.flux-system.svc.cluster.local./gitrepository/flux-system/flux-system/6554ea6324d70caf0f2dfa200e137fd9c2aecc8a.tar.gz": dial tcp 10.0.165.86:80: i/o timeout

Same error exists while checking the Kustomization pod as below: #kubectl logs kustomize-controller-7f5455cd78-wwxhk -n flux-system
"level":"error","ts":"2021-01-14T09:04:52.524Z","logger":"controller","msg":"Reconciler error","reconcilerGroup":"kustomize.toolkit.fluxcd.io","reconcilerKind":"Kustomization","controller":"kustomization","name":"flux-system","namespace":"flux-system","error":"failed to download artifact from http://source-controller.flux-system.svc.cluster.local./gitrepository/flux-system/flux-system/6554ea6324d70caf0f2dfa200e137fd9c2aecc8a.tar.gz, error: Get "http://source-controller.flux-system.svc.cluster.local./gitrepository/flux-system/flux-system/6554ea6324d70caf0f2dfa200e137fd9c2aecc8a.tar.gz": dial tcp 10.0.165.86:80: i/o timeout"}

Thanks for any helpful advice.
bug blocked-upstream
opened by mazen-bassiouny 47
Bootstrap fails the first time
Describe the bug

When running bootstrap on a github repository it seems to always fail the first time with:

installing components in "flux-system" namespace Kustomization/flux-system/flux-system dry-run failed, error: no matches for kind "Kustomization" in version "kustomize.toolkit.fluxcd.io/v1beta2"

After running the exact same bootstrap command again it works as expected. The bootstrap command is flux bootstrap github --owner=*** --repository=*** --path=some/repo/path --personal

Any ideas what this might be about?

Steps to reproduce

N/A

Expected behavior

N/A

Screenshots and recordings

No response

OS / Distro

Windows 10

Flux version

0.25.3

Flux check

N/A

Git provider

github

Container Registry provider

No response

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct
opened by mibollma 30

Two PVC-s bound to the same PV

Describe the bug

Hello team,

Reconciliation process creates new pod before deleting old one. In case of pod has pvc in volume-section that ordering creates double claim to the same pv. IMO order of operations should be

remove old pod
create new one

Steps to reproduce

Easiest way to reproduce is to follow "Automate image updates to Git" guide , with the following addition to podinfo-deployment.yaml.

Step 1) Add PV / PVC and attach volume to pod.

      volumes:
        - name: empty-dir-vol
          persistentVolumeClaim:
            claimName: empty-dir-pvc
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: empty-dir-pvc
  namespace: podinfo-image-updater
spec:
  storageClassName: slow
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 3Gi
---
apiVersion: v1
kind: PersistentVolume
metadata:
  labels:
    type: nfs
  name: podinfoimageupdater-emptydir-pv
spec:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 10Gi
  claimRef:
    name: empty-dir-pvc
    namespace: podinfo-image-updater
  nfs:
    path: /storage_local/podinfo-image-updater/empty-dir
    server: 192.168.170.36
  storageClassName: slow

If it is confusing full manifest is here

Change image version to trigger deployment reconciliation
Observe the problem. PVC will get to Lost state

$ kubectl get pvc -w
NAME            STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
empty-dir-pvc   Bound     podinfoimageupdater-emptydir-pv   10Gi       RWO            slow           11s
empty-dir-pvc   Lost      podinfoimageupdater-emptydir-pv   0                         slow           2m26s

[email protected]:~$ microk8s.kubectl describe pvc 
Name:          empty-dir-pvc
Namespace:     podinfo-image-updater
StorageClass:  slow
Status:        Lost
Volume:        podinfoimageupdater-emptydir-pv
Labels:        kustomize.toolkit.fluxcd.io/name=flux-system
               kustomize.toolkit.fluxcd.io/namespace=flux-system
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      0
Access Modes:  
VolumeMode:    Filesystem
Used By:       podinfo-9ccf96ff5-6d8nx    <----------- notice podID
Events:
  Type     Reason         Age   From                         Message
  ----     ------         ----  ----                         -------
  Warning  ClaimMisbound  26s   persistentvolume-controller  Two claims are bound to the same volume, this one is bound incorrectly

PV will get to Available state

$ kubectl get pv -w
podinfoimageupdater-emptydir-pv     10Gi       RWO            Retain           Bound       podinfo-image-updater/empty-dir-pvc   slow                    2m23s
podinfoimageupdater-emptydir-pv     10Gi       RWO            Retain           Available   podinfo-image-updater/empty-dir-pvc   slow                    2m23s

Reason for that is order of pod update operations

$ kubectl get pod -w
NAME                       READY   STATUS    RESTARTS       AGE
podinfo-844777597c-hhj8g   1/1     Running   1 (114m ago)   11h <----- this pod owns PVC
podinfo-9ccf96ff5-6d8nx    0/1     Pending   0              0s
podinfo-9ccf96ff5-6d8nx    0/1     Pending   0              0s
podinfo-9ccf96ff5-6d8nx    0/1     Pending   0              14s
podinfo-9ccf96ff5-6d8nx    0/1     ContainerCreating   0              14s
podinfo-9ccf96ff5-6d8nx    0/1     ContainerCreating   0              15s
podinfo-9ccf96ff5-6d8nx    1/1     Running             0              15s   <--------- this pod creates duplicate PVC
podinfo-844777597c-hhj8g   1/1     Terminating         1 (116m ago)   11h
podinfo-844777597c-hhj8g   0/1     Terminating         1 (116m ago)   11h
podinfo-844777597c-hhj8g   0/1     Terminating         1 (116m ago)   11h
podinfo-844777597c-hhj8g   0/1     Terminating         1 (116m ago)   11h

Expected behavior

Successful image update even with PV/PVC attached to the pod

Screenshots and recordings

No response

OS / Distro

20.04.3 LTS (Focal Fossa)

Flux version

flux version 0.27.0

Flux check

$ flux check ► checking prerequisites ✔ Kubernetes 1.22.6-3+7ab10db7034594 >=1.20.6-0 ► checking controllers ✔ helm-controller: deployment ready ► ghcr.io/fluxcd/helm-controller:v0.17.0 ✔ notification-controller: deployment ready ► ghcr.io/fluxcd/notification-controller:v0.22.0 ✔ image-reflector-controller: deployment ready ► ghcr.io/fluxcd/image-reflector-controller:v0.16.0 ✔ image-automation-controller: deployment ready ► ghcr.io/fluxcd/image-automation-controller:v0.20.0 ✔ kustomize-controller: deployment ready ► ghcr.io/fluxcd/kustomize-controller:v0.21.0 ✔ source-controller: deployment ready ► ghcr.io/fluxcd/source-controller:v0.21.2 ✔ all checks passed

Git provider

No response

Container Registry provider

No response

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct

opened by IvanKuchin 27

[Gitlab] flux bootstrap fails for personal projects if they already exist

When I try to update my flux v2 installation using the bootstrap command it fails with an error from gitlab:

failed to create project, error: POST https://gitlab.com/api/v4/projects: 400

I use the below bootstrap command to install / update flux v2, which worked until now:

[email protected]:~$ cat install-flux.sh 
curl -s https://toolkit.fluxcd.io/install.sh | sudo bash

export GITLAB_TOKEN=???????????????

flux bootstrap gitlab \
  --owner=isnull \
  --repository=myrepo \
  --branch=master \
  --path=k8 \
  --token-auth \
  --personal

Executing the flux bootstrap yields the error:

[email protected]:~$ sh install-flux.sh 
[INFO]  Downloading metadata https://api.github.com/repos/fluxcd/flux2/releases/latest
[INFO]  Using 0.7.4 as release
[INFO]  Downloading hash https://github.com/fluxcd/flux2/releases/download/v0.7.4/flux_0.7.4_checksums.txt
[INFO]  Downloading binary https://github.com/fluxcd/flux2/releases/download/v0.7.4/flux_0.7.4_linux_amd64.tar.gz
[INFO]  Verifying binary download
[INFO]  Installing flux to /usr/local/bin/flux
► connecting to gitlab.com
✗ failed to create project, error: POST https://gitlab.com/api/v4/projects: 400 {message: {limit_reached: []}, {name: [has already been taken]}, {path: [has already been taken]}}

Sys info:

[email protected]:~$ flux check
► checking prerequisites
✔ kubectl 1.20.2 >=1.18.0
✔ Kubernetes 1.19.5-34+8af48932a5ef06 >=1.16.0
► checking controllers
✔ source-controller is healthy
► ghcr.io/fluxcd/source-controller:v0.5.6
✔ kustomize-controller is healthy
► ghcr.io/fluxcd/kustomize-controller:v0.5.3
✔ helm-controller is healthy
► ghcr.io/fluxcd/helm-controller:v0.4.4
✔ notification-controller is healthy
► ghcr.io/fluxcd/notification-controller:v0.5.0
✔ all checks passed

Maybe some Gitlab project api change caused this?

opened by IsNull 24

ImageRepository manifests ignoring spec.secretRef changes
Describe the bug

We noticed this issue after updating to v0.25.1 and the issue is not currently effecting one of our other clusters that is on v0.24.1

when making changes to our image repository manifests we noticed that despite the reconciliation passing without issue the spec.secretRef field was not effected example.

Git Version

apiVersion: image.toolkit.fluxcd.io/v1beta1 kind: ImageRepository metadata: name: some-app namespace: flux-system spec: image: <ECR_URL>/some-app interval: 5m

Cluster Version

apiVersion: image.toolkit.fluxcd.io/v1beta1 kind: ImageRepository metadata: name: some-app namespace: flux-system spec: image: <ECR_URL>/some-app interval: 5m secretRef: name: ecr-credentials

Steps to reproduce

add a spec.secretRef section to an existing ImageRepository manifest

commit to git

watch reconciliation pass successfully

remove field

watch reconciliation pass successfully

see that spec.secretRef has not been removed

Expected behavior

I expect that when removing the spec.secretRef for the sync process to remove it on the cluster as well or error if there is a reason it cannot be edited/applied.

Screenshots and recordings

No response

OS / Distro

N/A

Flux version

v.0.25.1

Flux check

► checking prerequisites ✔ Kubernetes 1.21.5 >=1.19.0-0 ► checking controllers ✔ helm-controller: deployment ready ► ghcr.io/fluxcd/helm-controller:v0.15.0 ✔ image-automation-controller: deployment ready ► ghcr.io/fluxcd/image-automation-controller:v0.19.0 ✔ image-reflector-controller: deployment ready ► ghcr.io/fluxcd/image-reflector-controller:v0.15.0 ✔ kustomize-controller: deployment ready ► ghcr.io/fluxcd/kustomize-controller:v0.19.0 ✔ notification-controller: deployment ready ► ghcr.io/fluxcd/notification-controller:v0.20.1 ✔ source-controller: deployment ready ► ghcr.io/fluxcd/source-controller:v0.20.1 ✔ all checks passed

Git provider

gitlab

Container Registry provider

ECR

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct
opened by stvnksslr 22
Feature request: `flux render {kustomization|helmrelease}`
Debugging configuration examples would benefit with a new render subcommand to flux whereby the fully rendered manifests defined by a Kustomization or HelmRelease object are output. You'd run

flux render kustomization my-app

and get the streamed manifests as they were (our would have been except for an error) applied to K8S.
opened by metasim 22
Flux ignores kustomization.yaml
Describe the bug

After recently deploying a new cluster with GKE version 1.22 I receive the error below:

Kustomization/flux-system/${environment} dry-run failed, reason: Invalid, error: Kustomization.kustomize.toolkit.fluxcd.io "${environment}" is invalid: metadata.name: Invalid value: "${environment}": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

It seems that that kustomization.yaml file is somehow completely ignored. Because I compared contents of all the patch targets and they are clearly not patched.

When, I assume, trying to deploy this:

apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 kind: Kustomization metadata: name: ${environment} namespace: flux-system spec: prune: True interval: 1m dependsOn: - name: namespaces - .... path: environments/${environment}/application sourceRef: kind: GitRepository name: flux-system namespace: flux-system postBuild: substitute: environment: ${environment}

Steps to reproduce

Kubernetes version 1.22.12-gke.1200 - I am not sure about this step but that it is the only significant change at that stage

kustomization.yaml:

# This manifest was generated by Terraform. DO NOT EDIT. # Modify this file through the flux module apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: - gotk-sync.yaml - gotk-components.yaml patches: - target: version: v1beta2 group: kustomize.toolkit.fluxcd.io kind: Kustomization name: flux-system namespace: flux-system patch: |- - op: add path: /spec/postBuild value: substitute: environment: "dev"

Expected behavior

Flux should pickup kustomization.yaml and apply all the patches in it.

Screenshots and recordings

No response

OS / Distro

WSL2, Kubernetes version 1.22.12-gke.1200

Flux version

v0.31.5, v0.35.0

Flux check

flux check ► checking prerequisites ✗ flux 0.31.5 <0.35.0 (new version is available, please upgrade) W1013 11:21:43.198854 10069 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead. To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke ✔ Kubernetes 1.22.12-gke.1200 >=1.20.6-0 ► checking controllers ✔ helm-controller: deployment ready ► ghcr.io/fluxcd/helm-controller:v0.25.0 ✔ image-automation-controller: deployment ready ► ghcr.io/fluxcd/image-automation-controller:v0.26.0 ✔ image-reflector-controller: deployment ready ► ghcr.io/fluxcd/image-reflector-controller:v0.22.0 ✔ kustomize-controller: deployment ready ► ghcr.io/fluxcd/kustomize-controller:v0.29.0 ✔ notification-controller: deployment ready ► ghcr.io/fluxcd/notification-controller:v0.27.0 ✔ source-controller: deployment ready ► ghcr.io/fluxcd/source-controller:v0.30.0 ► checking crds ✔ alerts.notification.toolkit.fluxcd.io/v1beta1 ✔ buckets.source.toolkit.fluxcd.io/v1beta2 ✔ gitrepositories.source.toolkit.fluxcd.io/v1beta2 ✔ helmcharts.source.toolkit.fluxcd.io/v1beta2 ✔ helmreleases.helm.toolkit.fluxcd.io/v2beta1 ✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2 ✔ imagepolicies.image.toolkit.fluxcd.io/v1beta1 ✔ imagerepositories.image.toolkit.fluxcd.io/v1beta1 ✔ imageupdateautomations.image.toolkit.fluxcd.io/v1beta1 ✔ kustomizations.kustomize.toolkit.fluxcd.io/v1beta2 ✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2 ✔ providers.notification.toolkit.fluxcd.io/v1beta1 ✔ receivers.notification.toolkit.fluxcd.io/v1beta1 ✔ all checks passed

Git provider

GitHub

Container Registry provider

ghcr.io

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct
opened by ar-qun 21

Bootstrap creates empty files

Bootstrap command doesn't want to install on existing GIT repository. I can live with it, so I've decided to allow it create new repository. Here's a log of creation:

 $ flux bootstrap github   --token-auth   --hostname=github.tools.xxx   --owner=yyyy   --repository=kubernetes-config2   --branch=master   --path=/clusters/k3sdev   --team=zzzz
► connecting to github.tools.xxx
✔ repository created
✔ zzzz team access granted
✔ repository cloned
✚ generating manifests
✔ components manifests pushed
► installing components in flux-system namespace
namespace/flux-system created
networkpolicy.networking.k8s.io/allow-scraping created
networkpolicy.networking.k8s.io/allow-webhooks created
networkpolicy.networking.k8s.io/deny-ingress created
role.rbac.authorization.k8s.io/crd-controller-flux-system created
rolebinding.rbac.authorization.k8s.io/crd-controller-flux-system created
clusterrolebinding.rbac.authorization.k8s.io/cluster-reconciler-flux-system created
customresourcedefinition.apiextensions.k8s.io/buckets.source.toolkit.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/gitrepositories.source.toolkit.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/helmcharts.source.toolkit.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/helmrepositories.source.toolkit.fluxcd.io created
service/source-controller created
deployment.apps/source-controller created
customresourcedefinition.apiextensions.k8s.io/kustomizations.kustomize.toolkit.fluxcd.io created
deployment.apps/kustomize-controller created
customresourcedefinition.apiextensions.k8s.io/helmreleases.helm.toolkit.fluxcd.io created
deployment.apps/helm-controller created
customresourcedefinition.apiextensions.k8s.io/alerts.notification.toolkit.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/providers.notification.toolkit.fluxcd.io created
customresourcedefinition.apiextensions.k8s.io/receivers.notification.toolkit.fluxcd.io created
service/notification-controller created
service/webhook-receiver created
deployment.apps/notification-controller created
Waiting for deployment "source-controller" rollout to finish: 0 of 1 updated replicas are available...
deployment "source-controller" successfully rolled out
deployment "kustomize-controller" successfully rolled out
deployment "helm-controller" successfully rolled out
Waiting for deployment "notification-controller" rollout to finish: 0 of 1 updated replicas are available...
deployment "notification-controller" successfully rolled out
✔ install completed
► generating sync manifests
✔ sync manifests pushed
► applying sync manifests
◎ waiting for cluster sync
✗ kustomization path not found: stat /tmp/flux-system309109433/clusters/k3sdev: no such file or directory

Repository has been created, README.md is created, but yaml files are empty. Should they? Listing logs repository shows:

$ git log -p
commit cf5e74b0428674aced9f2fd1b45f7d147991fb40 (HEAD -> master, origin/master, origin/HEAD)
Author: flux <xxxx>
Date:   Fri Dec 11 10:58:55 2020 +0100

    Add manifests

commit bea83df32c89baeec8031da2235b83504a43c6c3
Author: flux <xxxx>
Date:   Fri Dec 11 10:58:35 2020 +0100

    Add manifests

commit 0bd99a15329e3370dcf82833455e82efb8ff35d7
Author: xxxx <xxxx>
Date:   Fri Dec 11 10:58:31 2020 +0100

    Initial commit

bug area/bootstrap

opened by Marx2 21

Kustomizations without a base do not apply
Describe the bug

according to the FAQ we should be able to patch arbitrary pre-installed resources using kustomize objects.

I have not been able to patch any using the (limited) instructions in the FAQ.

Steps to reproduce

install flux

create kustomization with patchesStrategicMerge

reconcile kustomization

Expected behavior

resource patched with provided patch

Screenshots and recordings

kustomization:

apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization patches: - path: weave-liveness.yaml target: kind: DaemonSet name: weave-net namespace: kube-system

weave-liveness.yaml:

apiVersion: apps/v1 kind: DaemonSet metadata: annotations: kustomize.fluxcd.toolkit.io/ssa: merge name: weave-net namespace: kube-system spec: template: spec: containers: - name: weave livenessProbe: exec: command: - /bin/sh - -c - /home/weave/weave --local status connections | grep fastdp initialDelaySeconds: 20 periodSeconds: 5

no errors, but also no change / no output.

# kubectl get kustomizations.kustomize.toolkit.fluxcd.io -n flux-system weave-net NAME AGE READY STATUS weave-net 22h True Applied revision: main/ca160ca0ec5d1ef98cb6fc368d09e6e09195f1ab

OS / Distro

centos 7.7

Flux version

v0.28.4

Flux check

flux check

► checking prerequisites ✔ Kubernetes 1.23.3 >=1.20.6-0 ► checking controllers ✔ helm-controller: deployment ready ► car:5000/helm-controller:v0.18.2 ✔ image-automation-controller: deployment ready ► car:5000/image-automation-controller:v0.21.2 ✔ image-reflector-controller: deployment ready ► car:5000/image-reflector-controller:v0.17.1 ✔ kustomize-controller: deployment ready ► car:5000/kustomize-controller:v0.22.2 ✔ notification-controller: deployment ready ► car:5000/notification-controller:v0.23.1 ✔ source-controller: deployment ready ► car:5000/source-controller:v0.22.4 ✔ all checks passed

Git provider

No response

Container Registry provider

No response

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct
opened by daveoy 20

Bootstrapping new cluster fails on k3s v1.20

I have a k3s cluster working on a Raspberry Pi connected to my home local network. Tried to bootstrap a new GOTK repo using the following command:

flux bootstrap github \
--owner=$GITHUB_USER \
--repository=$CONFIG_REPO \
--branch=master \
--path=./clusters/my-cluster \
--personal \
--kubeconfig=/etc/rancher/k3s/k3s.yaml

The output for the bootstrapping command (notice the "context deadline exceeded" after "waiting for Kustomization "flux-system/flux-system" to be reconciled"):

► connecting to github.com
► cloning branch "master" from Git repository "https://github.com/argamanza/raspberry-pi-flux-config.git"
✔ cloned repository
► generating component manifests
✔ generated component manifests
✔ component manifests are up to date
► installing toolkit.fluxcd.io CRDs
◎ waiting for CRDs to be reconciled
✔ CRDs reconciled successfully
► installing components in "flux-system" namespace
✔ installed components
✔ reconciled components
► determining if source secret "flux-system/flux-system" exists
✔ source secret up to date
► generating sync manifests
✔ generated sync manifests
✔ sync manifests are up to date
► applying sync manifests
✔ reconciled sync configuration
◎ waiting for Kustomization "flux-system/flux-system" to be reconciled
✗ context deadline exceeded
► confirming components are healthy
✔ source-controller: deployment ready
✔ kustomize-controller: deployment ready
✔ helm-controller: deployment ready
✔ notification-controller: deployment ready
✔ all components are healthy
✗ bootstrap failed with 1 health check failure(s)

The logs for the Kustomize Controller expose what the issue might be:

{"level":"info","ts":"2021-04-24T20:55:51.200Z","logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":":8080"}
{"level":"info","ts":"2021-04-24T20:55:51.202Z","logger":"setup","msg":"starting manager"}
I0424 20:55:51.206769       7 leaderelection.go:243] attempting to acquire leader lease flux-system/kustomize-controller-leader-election...
{"level":"info","ts":"2021-04-24T20:55:51.307Z","msg":"starting metrics server","path":"/metrics"}
I0424 20:56:30.436269       7 leaderelection.go:253] successfully acquired lease flux-system/kustomize-controller-leader-election
{"level":"info","ts":"2021-04-24T20:56:30.436Z","logger":"controller.kustomization","msg":"Starting EventSource","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-04-24T20:56:30.437Z","logger":"controller.kustomization","msg":"Starting EventSource","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-04-24T20:56:30.538Z","logger":"controller.kustomization","msg":"Starting EventSource","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-04-24T20:56:30.639Z","logger":"controller.kustomization","msg":"Starting Controller","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization"}
{"level":"info","ts":"2021-04-24T20:56:30.639Z","logger":"controller.kustomization","msg":"Starting workers","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","worker count":4}
{"level":"info","ts":"2021-04-24T20:56:47.576Z","logger":"controller.kustomization","msg":"Kustomization applied in 2.713132582s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"flux-system","namespace":"flux-system","output":{"clusterrole.rbac.authorization.k8s.io/crd-controller-flux-system":"unchanged","clusterrolebinding.rbac.authorization.k8s.io/cluster-reconciler-flux-system":"unchanged","clusterrolebinding.rbac.authorization.k8s.io/crd-controller-flux-system":"unchanged","customresourcedefinition.apiextensions.k8s.io/alerts.notification.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/buckets.source.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/gitrepositories.source.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/helmcharts.source.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/helmreleases.helm.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/helmrepositories.source.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/kustomizations.kustomize.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/providers.notification.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/receivers.notification.toolkit.fluxcd.io":"configured","deployment.apps/helm-controller":"configured","deployment.apps/kustomize-controller":"configured","deployment.apps/notification-controller":"configured","deployment.apps/source-controller":"configured","gitrepository.source.toolkit.fluxcd.io/flux-system":"unchanged","kustomization.kustomize.toolkit.fluxcd.io/flux-system":"unchanged","namespace/flux-system":"unchanged","networkpolicy.networking.k8s.io/allow-egress":"unchanged","networkpolicy.networking.k8s.io/allow-scraping":"unchanged","networkpolicy.networking.k8s.io/allow-webhooks":"unchanged","service/notification-controller":"unchanged","service/source-controller":"unchanged","service/webhook-receiver":"unchanged","serviceaccount/helm-controller":"unchanged","serviceaccount/kustomize-controller":"unchanged","serviceaccount/notification-controller":"unchanged","serviceaccount/source-controller":"unchanged"}}
{"level":"error","ts":"2021-04-24T20:56:47.609Z","logger":"controller.kustomization","msg":"unable to update status after reconciliation","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"flux-system","namespace":"flux-system","error":"Kustomization.kustomize.toolkit.fluxcd.io \"flux-system\" is invalid: status.snapshot.entries.namespace: Invalid value: \"null\": status.snapshot.entries.namespace in body must be of type string: \"null\""}
{"level":"error","ts":"2021-04-24T20:56:47.609Z","logger":"controller.kustomization","msg":"Reconciler error","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"flux-system","namespace":"flux-system","error":"Kustomization.kustomize.toolkit.fluxcd.io \"flux-system\" is invalid: status.snapshot.entries.namespace: Invalid value: \"null\": status.snapshot.entries.namespace in body must be of type string: \"null\""}
{"level":"info","ts":"2021-04-24T20:56:53.835Z","logger":"controller.kustomization","msg":"Kustomization applied in 2.470822475s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"flux-system","namespace":"flux-system","output":{"clusterrole.rbac.authorization.k8s.io/crd-controller-flux-system":"unchanged","clusterrolebinding.rbac.authorization.k8s.io/cluster-reconciler-flux-system":"unchanged","clusterrolebinding.rbac.authorization.k8s.io/crd-controller-flux-system":"unchanged","customresourcedefinition.apiextensions.k8s.io/alerts.notification.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/buckets.source.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/gitrepositories.source.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/helmcharts.source.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/helmreleases.helm.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/helmrepositories.source.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/kustomizations.kustomize.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/providers.notification.toolkit.fluxcd.io":"configured","customresourcedefinition.apiextensions.k8s.io/receivers.notification.toolkit.fluxcd.io":"configured","deployment.apps/helm-controller":"configured","deployment.apps/kustomize-controller":"configured","deployment.apps/notification-controller":"configured","deployment.apps/source-controller":"configured","gitrepository.source.toolkit.fluxcd.io/flux-system":"unchanged","kustomization.kustomize.toolkit.fluxcd.io/flux-system":"unchanged","namespace/flux-system":"unchanged","networkpolicy.networking.k8s.io/allow-egress":"unchanged","networkpolicy.networking.k8s.io/allow-scraping":"unchanged","networkpolicy.networking.k8s.io/allow-webhooks":"unchanged","service/notification-controller":"unchanged","service/source-controller":"unchanged","service/webhook-receiver":"unchanged","serviceaccount/helm-controller":"unchanged","serviceaccount/kustomize-controller":"unchanged","serviceaccount/notification-controller":"unchanged","serviceaccount/source-controller":"unchanged"}}
{"level":"error","ts":"2021-04-24T20:56:53.863Z","logger":"controller.kustomization","msg":"unable to update status after reconciliation","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"flux-system","namespace":"flux-system","error":"Kustomization.kustomize.toolkit.fluxcd.io \"flux-system\" is invalid: status.snapshot.entries.namespace: Invalid value: \"null\": status.snapshot.entries.namespace in body must be of type string: \"null\""}

From the logs I can tell that status.snapshot.entries.namespace shouldn't be null for the flux-system kustomization, and after testing the same bootstrap procedure on a local machine using cluster I provisioned using kind I can see that the kustomization indeed miss the status.snapshot data in the K3S cluster while on my local kind cluster it exists:

[email protected]:

kubectl describe kustomization flux-system -n flux-system

Name:         flux-system
Namespace:    flux-system
Labels:       kustomize.toolkit.fluxcd.io/checksum=1d4c5beef02b0043768a476cc3fed578aa3ed6f0
              kustomize.toolkit.fluxcd.io/name=flux-system
              kustomize.toolkit.fluxcd.io/namespace=flux-system
Annotations:  <none>
API Version:  kustomize.toolkit.fluxcd.io/v1beta1
Kind:         Kustomization
Metadata:
  Creation Timestamp:  2021-04-24T19:42:50Z
  Finalizers:
    finalizers.fluxcd.io
  Generation:  1
...
...
Status:
  Conditions:
    Last Transition Time:  2021-04-24T19:43:30Z
    Message:               reconciliation in progress
    Reason:                Progressing
    Status:                Unknown
    Type:                  Ready
Events:
  Type    Reason  Age   From                  Message
  ----    ------  ----  ----                  -------
  Normal  info    57m   kustomize-controller  customresourcedefinition.apiextensions.k8s.io/buckets.source.toolkit.fluxcd.io configured
...

[email protected]:

kubectl describe kustomization flux-system -n flux-system

Name:         flux-system
Namespace:    flux-system
Labels:       kustomize.toolkit.fluxcd.io/checksum=1d4c5beef02b0043768a476cc3fed578aa3ed6f0
              kustomize.toolkit.fluxcd.io/name=flux-system
              kustomize.toolkit.fluxcd.io/namespace=flux-system
Annotations:  <none>
API Version:  kustomize.toolkit.fluxcd.io/v1beta1
Kind:         Kustomization
Metadata:
  Creation Timestamp:  2021-04-25T12:35:37Z
  Finalizers:
    finalizers.fluxcd.io
  Generation:  1
...
...
Status:
  Conditions:
    Last Transition Time:   2021-04-25T12:37:02Z
    Message:                Applied revision: master/dbce13415e4118bb071b58dab20d1f2bec527a14
    Reason:                 ReconciliationSucceeded
    Status:                 True
    Type:                   Ready
  Last Applied Revision:    master/dbce13415e4118bb071b58dab20d1f2bec527a14
  Last Attempted Revision:  master/dbce13415e4118bb071b58dab20d1f2bec527a14
  Observed Generation:      1
  Snapshot:
    Checksum:  1d4c5beef02b0043768a476cc3fed578aa3ed6f0
    Entries:
      Kinds:
        /v1, Kind=Namespace:                                     Namespace
        apiextensions.k8s.io/v1, Kind=CustomResourceDefinition:  CustomResourceDefinition
        rbac.authorization.k8s.io/v1, Kind=ClusterRole:          ClusterRole
        rbac.authorization.k8s.io/v1, Kind=ClusterRoleBinding:   ClusterRoleBinding
      Namespace:
      Kinds:
        /v1, Kind=Service:                                        Service
        /v1, Kind=ServiceAccount:                                 ServiceAccount
        apps/v1, Kind=Deployment:                                 Deployment
        kustomize.toolkit.fluxcd.io/v1beta1, Kind=Kustomization:  Kustomization
        networking.k8s.io/v1, Kind=NetworkPolicy:                 NetworkPolicy
        source.toolkit.fluxcd.io/v1beta1, Kind=GitRepository:     GitRepository
      Namespace:                                                  flux-system
Events:
  Type    Reason  Age    From                  Message
  ----    ------  ----   ----                  -------
  Normal  info    3m53s  kustomize-controller  customresourcedefinition.apiextensions.k8s.io/buckets.source.toolkit.fluxcd.io configured
...

This is also where my debugging process came to a dead end as I couldn't find a reason why the status.snapshot doesn't populate on my [email protected] while it does on [email protected] using the same bootstrap process.

I believe the fact that the issue only occurs on my raspberry pi implies that it might be a networking issue of some kind that prevents the kustomize controller from getting status updates from GitHub and I need to handle port forwarding or something similar, but I'm not sure.

Kubernetes version: v1.20.6+k3s1
Git provider: GitHub

flux --version
flux version 0.13.1

flux check
► checking prerequisites
✔ kubectl 1.20.6+k3s1 >=1.18.0-0
✔ Kubernetes 1.20.6+k3s1 >=1.16.0-0
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.10.0
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v0.11.1
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v0.13.0
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v0.12.1
✔ all checks passed

blocked-upstream

opened by argamanza 20

custom port is not honored for ssh based git url

I am trying to do a bootstrap of flux on to a new cluster, but the git server I have uses a custom port for its ssh access, and flux bootstrap seems to strip the port off, causing the initial clone to fail.

I found the line in the git bootstrap below, which seems to have actually been changed in the past so custom ports are allowed for http/s.

Not sure whether this is intended for ssh (I don't see why), but perhaps this can be changed. I would have done the change myself but I don't know whether there is a reason it is this way now.

https://github.com/fluxcd/flux2/blob/18c944d18a6272e4c6fb26116a9db02ba4deb937/cmd/flux/bootstrap_git.go#L190
area/bootstrap

opened by sartsj 19
Generated secrets contain newline
Describe the bug

Kubernetes secrets generated by secretGenerator contain newlines.

Steps to reproduce

sops secrets/test

Save it without any newline.

Add a kustomization with the following:

secretGenerator: - files: - secrets/test name: test-secret

The Kubernetes secret contains a newline:

Expected behavior

The secret should not contain a newline.

Screenshots and recordings

No response

OS / Distro

Amazon EKS optimized Amazon Linux AMIs

Flux version

0.38.2

Flux check

N/A

Git provider

No response

Container Registry provider

No response

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct
opened by mjroeleveld 0
Kustomize key `specs.suspend` does not get removed by flux on a flux-created kustomization resource after being manually added on the cluster.
Describe the bug

Flux does not properly revert a manually changed kustomization resource back to what was defined in the GitOps repository. If one uses a bootstrap approach to create multiple kustomization resources from their definitions in the GitOps repository, flux will not remove a manually added specs.suspend key. This is the case even if the bootstrap resource has spec.prune=true.

Steps to reproduce

Create bootstrap kustomization resources with spec.prune=true, which creates a set of kustomization resources defined in the GitOps repository

flux create kustomization bootstrap \ --path="./clusters/<device-ID>/flux" \ --source=gitops-source \ --prune=true \ --interval=1m

Simplified GitOps repository folder structure:

. ├── apps └── clusters └── <device-ID> ├── flux │ ├── sets-1.yaml │ └── sets-2.yaml └── sets └── sets-1 └── sets-2

eg. Kustomization resource definition pointing to clusters/<device-ID>/sets/sets-1 defined in the manifest file clusters/<device-ID>/flux/sets-1.yaml

apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 kind: Kustomization metadata: name: <device-ID>-sets-1 namespace: flux-system spec: interval: 1m sourceRef: kind: GitRepository name: gitops-repo namespace: flux-system path: ./clusters/<device-ID>/sets/sets-1 prune: true wait: true timeout: 10m

The key spec.suspend is not specified in any of the resource definitions of the kustomization resources in the GitOps repo. As expected neither is the spec.suspend key set for the created kustomization resources on the cluster, when checking with kubectl.

Manually suspend the kustomization resource with flux suspend on the cluster. This will add the spec.suspend=true to the kustomization resource.

flux suspend kustomization <device-ID>-sets-1

After reconciliation the suspend key does not get removed from the kustomization resource. The resource's state on the cluster is therefore different from what is defined in the GitOps repository.

Expected behavior

Flux would revert the kustomization resource to how it was defined in the GitOps repository. Which would mean in this case removing the added spec.suspend=true from the resource.

The change only gets reverted back, if the kustomization resource definition in clusters/flux/ has a reference to spec.suspend.

Screenshots and recordings

Flux would revert the kustomization resource to how it was defined in the GitOps repository. Which would mean in this case removing the added spec.suspend=true from the resource.

The change only gets reverted back, if the kustomization resource definition in clusters/flux/ has a reference to spec.suspend.

OS / Distro

Ubuntu 20.04

Flux version

v0.37.0

Flux check

► checking prerequisites ✗ flux 0.37.0 <0.38.2 (new version is available, please upgrade) ✔ Kubernetes 1.25.4+k3s1 >=1.20.6-0 ► checking controllers ✔ kustomize-controller: deployment ready ► mcr.microsoft.com/oss/fluxcd/kustomize-controller:v0.31.0 ✔ notification-controller: deployment ready ► mcr.microsoft.com/oss/fluxcd/notification-controller:v0.29.0 ✔ helm-controller: deployment ready ► mcr.microsoft.com/oss/fluxcd/helm-controller:v0.27.0 ✔ source-controller: deployment ready ► mcr.microsoft.com/oss/fluxcd/source-controller:v0.32.1 ✔ fluxconfig-controller: deployment ready ► mcr.microsoft.com/azurek8sflux/fluxconfig-controller:1.6.3 ► mcr.microsoft.com/azurek8sflux/fluent-bit:1.6.3 ✔ fluxconfig-agent: deployment ready ► mcr.microsoft.com/azurek8sflux/fluxconfig-agent:1.6.3 ► mcr.microsoft.com/azurek8sflux/fluent-bit:1.6.3 ► checking crds ✔ fluxconfigs.clusterconfig.azure.com/v1alpha1 ✔ helmreleases.helm.toolkit.fluxcd.io/v2beta1 ✔ imagepolicies.image.toolkit.fluxcd.io/v1beta1 ✔ imagerepositories.image.toolkit.fluxcd.io/v1beta1 ✔ imageupdateautomations.image.toolkit.fluxcd.io/v1beta1 ✔ kustomizations.kustomize.toolkit.fluxcd.io/v1beta2 ✔ alerts.notification.toolkit.fluxcd.io/v1beta1 ✔ providers.notification.toolkit.fluxcd.io/v1beta1 ✔ receivers.notification.toolkit.fluxcd.io/v1beta1 ✔ buckets.source.toolkit.fluxcd.io/v1beta2 ✔ gitrepositories.source.toolkit.fluxcd.io/v1beta2 ✔ helmcharts.source.toolkit.fluxcd.io/v1beta2 ✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2 ✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2 ✔ all checks passed

Git provider

No response

Container Registry provider

No response

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct
opened by MahrRah 1

kustomization error

Describe the bug

I added this to the exclusionList of an Alert:

"ImageRepository\.image\.toolkit\.fluxcd\.io \".*\" not found"

And that caused the kustomization-controller to fail with this:

{"level":"error","ts":"2023-01-03T04:56:21.911Z","msg":"Reconciler error","controller":"kustomization","controllerGroup":"kustomize.toolkit.fluxcd.io","controllerKind":"Kustomization","Kustomization":{"name":"flux-system","namespace":"flux-system"},"namespace":"flux-system","name":"flux-system","reconcileID":"f05372d4-cb4d-409e-80dd-d185b42f009e","error":"panic: runtime error: invalid memory address or nil pointer dereference [recovered]"}
E0103 04:56:45.994483       8 runtime.go:79] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 309 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x1eaf2e0?, 0x380e010})
    k8s.io/[email protected]/pkg/util/runtime/runtime.go:75 +0x99
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile.func1()
    sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:110 +0xb9
panic({0x1eaf2e0, 0x380e010})
    runtime/panic.go:884 +0x212
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.handleErr(0xc000959928)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/yaml.go:304 +0x6d
panic({0x1eaf2e0, 0x380e010})
    runtime/panic.go:884 +0x212
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.yaml_parser_split_stem_comment(0xc0005f6800, 0x38)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/parserc.go:789 +0x38
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.yaml_parser_parse_block_sequence_entry(0xc0005f6800, 0xc0005f6ab0, 0x70?)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/parserc.go:703 +0x1fb
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.yaml_parser_state_machine(0x0?, 0x5?)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/parserc.go:179 +0xcf
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.yaml_parser_parse(0xc000dd25a0?, 0x219edcc?)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/parserc.go:129 +0x8c
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).peek(0xc0005f6800)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:103 +0x30
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).sequence(0xc0005f6800)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:258 +0x115
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).parse(0xc0005f6800)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:154 +0xeb
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).parseChild(0xc0005f6800?, 0xc000dc0320)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:194 +0x25
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).mapping(0xc0005f6800)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:285 +0x1d7
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).parse(0xc0005f6800)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:152 +0x105
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).parseChild(0xc0005f6800?, 0xc000dafb80)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:194 +0x25
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).mapping(0xc0005f6800)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:285 +0x1d7
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).parse(0xc0005f6800)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:152 +0x105
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).parseChild(...)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:194
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).document(0xc0005f6800)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:203 +0x85
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*parser).parse(0xc0005f6800)
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/decode.go:156 +0xae
sigs.k8s.io/kustomize/kyaml/internal/forked/github.com/go-yaml/yaml.(*Decoder).Decode(0xc000d05f90, {0x1fedce0?, 0xc000dafa40})
    sigs.k8s.io/kustomize/[email protected]/internal/forked/github.com/go-yaml/yaml/yaml.go:123 +0x136
sigs.k8s.io/kustomize/kyaml/kio.(*ByteReader).decode(0xc000959d68, {0xc000b00000, 0x430}, 0x26a86a0?, 0xc0008ec7b0?)
    sigs.k8s.io/kustomize/[email protected]/kio/byteio_reader.go:292 +0x79
sigs.k8s.io/kustomize/kyaml/kio.(*ByteReader).Read(0xc000959d68)
    sigs.k8s.io/kustomize/[email protected]/kio/byteio_reader.go:228 +0x371
sigs.k8s.io/kustomize/kyaml/kio.FromBytes({0xc000daa000, 0x895, 0x896})
    sigs.k8s.io/kustomize/[email protected]/kio/byteio_reader.go:110 +0xbb
sigs.k8s.io/kustomize/api/resource.(*Factory).RNodesFromBytes(0xc000fde360?, {0xc000daa000?, 0x26e0240?, 0x388af00?})
    sigs.k8s.io/kustomize/[email protected]/resource/factory.go:167 +0x30
sigs.k8s.io/kustomize/api/resource.(*Factory).SliceFromBytes(0xc0010b5a90?, {0xc000daa000?, 0x1d?, 0x26ac368?})
    sigs.k8s.io/kustomize/[email protected]/resource/factory.go:120 +0x38
github.com/fluxcd/pkg/kustomize.(*Generator).generateKustomization.func1.1({0xc0010b59a0, 0x4b}, {0x26d97c8?, 0xc000d0be10?}, {0x0?, 0x0?})
    github.com/fluxcd/pkg/[email protected]/kustomize_generator.go:451 +0x3e5
github.com/fluxcd/pkg/kustomize/filesys.fsSecure.Walk.func1({0xc0010b59a0, 0x4b}, {0x26d97c8, 0xc000d0be10}, {0x0, 0x0})
    github.com/fluxcd/pkg/[email protected]/filesys/fs_secure.go:241 +0x176
path/filepath.walk({0xc0010b59a0, 0x4b}, {0x26d97c8, 0xc000d0be10}, 0xc0002ce190)
    path/filepath/path.go:433 +0x123
path/filepath.walk({0xc000b3d180, 0x33}, {0x26d97c8, 0xc000e7a680}, 0xc0002ce190)
    path/filepath/path.go:457 +0x285
path/filepath.walk({0xc000346750, 0x2c}, {0x26d97c8, 0xc000f68a90}, 0xc0002ce190)
    path/filepath/path.go:457 +0x285
path/filepath.Walk({0xc000346750, 0x2c}, 0xc0002ce190)
    path/filepath/path.go:520 +0x6c
sigs.k8s.io/kustomize/kyaml/filesys.fsOnDisk.Walk(...)
    sigs.k8s.io/kustomize/[email protected]/filesys/fsondisk.go:138
github.com/fluxcd/pkg/kustomize/filesys.fsSecure.Walk({{0xc000fde360, 0x1d}, {0x26e0240, 0x388af00}, {0x0, 0x0, 0x0}}, {0xc000346750, 0x2c}, 0xc000b50340)
    github.com/fluxcd/pkg/ku[email protected]/filesys/fs_secure.go:243 +0xec
github.com/fluxcd/pkg/kustomize.(*Generator).generateKustomization.func1({0xc000346750, 0x2c})
    github.com/fluxcd/pkg/[email protected]/kustomize_generator.go:422 +0x151
github.com/fluxcd/pkg/kustomize.(*Generator).generateKustomization(0x1ebfd60?, {0xc000346750, 0x2c})
    github.com/fluxcd/pkg/[email protected]/kustomize_generator.go:465 +0x29b
github.com/fluxcd/pkg/kustomize.(*Generator).WriteFile(0xc00095bff8?, {0xc000346750, 0x2c}, {0x0, 0x0, 0x215e3c0?})
    github.com/fluxcd/pkg/[email protected]/kustomize_generator.go:112 +0x56
github.com/fluxcd/kustomize-controller/controllers.(*KustomizationReconciler).generate(0x384cec0?, {0x215e3c0?}, {0xc0005ba880?, 0xc0000f6f00?}, {0xc000346750?, 0x65?})
    github.com/fluxcd/kustomize-controller/controllers/kustomization_controller.go:559 +0x53
github.com/fluxcd/kustomize-controller/controllers.(*KustomizationReconciler).reconcile(0xc000cc8410, {0x26d43e8, 0xc0005bee70}, 0xc0000f6f00, {0x26d4810, 0xc000b0d680}, 0xc000a12970?)
    github.com/fluxcd/kustomize-controller/controllers/kustomization_controller.go:375 +0xc25
github.com/fluxcd/kustomize-controller/controllers.(*KustomizationReconciler).Reconcile(0xc000cc8410, {0x26d43e8, 0xc0005bee70}, {{{0xc000a12970?, 0x10?}, {0xc000a12960?, 0x40dc67?}}})
    github.com/fluxcd/kustomize-controller/controllers/kustomization_controller.go:263 +0x985
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile(0x26d4340?, {0x26d43e8?, 0xc0005bee70?}, {{{0xc000a12970?, 0x20ab920?}, {0xc000a12960?, 0x404554?}}})
    sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:121 +0xc8
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler(0xc000ce4140, {0x26d4340, 0xc000caaec0}, {0x1f4bb00?, 0xc000426a80?})
    sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:320 +0x33c
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem(0xc000ce4140, {0x26d4340, 0xc000caaec0})
    sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:273 +0x1d9
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2()
    sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:234 +0x85
created by sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2
    sigs.k8s.io/controller-r[email protected]/pkg/internal/controller/controller.go:230 +0x333

I'll understand if you close this as user error since clearly my regex is bad but I didn't figure it should crash this hard. I was unable to recover flux without running flux uninstall but I didn't try too hard to fix it before I ran the uninstall command.

Steps to reproduce

Install flux and create a notification configuration like this:

---
apiVersion: notification.toolkit.fluxcd.io/v1beta1
kind: Provider
metadata:
  name: slack
  namespace: flux-system
spec:
  type: slack
  channel: notifications
  address: https://hooks.slack.com/services/ABCD/EFGH
---
apiVersion: notification.toolkit.fluxcd.io/v1beta1
kind: Alert
metadata:
  name: errors-to-slack
  namespace: flux-system
spec:
  providerRef:
    name: slack
  eventSeverity: error
  eventSources:
    - kind: Bucket
      name: '*'
    - kind: GitRepository
      name: '*'
    - kind: Kustomization
      name: '*'
    - kind: HelmRelease
      name: '*'
    - kind: HelmChart
      name: '*'
    - kind: HelmRepository
      name: '*'
    - kind: ImageRepository
      name: '*'
    - kind: ImagePolicy
      name: '*'
    - kind: ImageUpdateAutomation
      name: '*'
  exclusionList:
    # ignore messages when something first enters the system
    - "version list argument cannot be empty"
    - "ImageRepository\.image\.toolkit\.fluxcd\.io \".*\" not found"

Expected behavior

Maybe log an error?

Screenshots and recordings

No response

OS / Distro

k3s on Debian

Flux version

0.38.2

Flux check

► checking prerequisites ✔ Kubernetes 1.25.4+k3s1 >=1.20.6-0 ► checking controllers ✔ helm-controller: deployment ready ► ghcr.io/fluxcd/helm-controller:v0.28.1 ✔ image-automation-controller: deployment ready ► ghcr.io/fluxcd/image-automation-controller:v0.28.0 ✔ image-reflector-controller: deployment ready ► ghcr.io/fluxcd/image-reflector-controller:v0.23.1 ✔ kustomize-controller: deployment ready ► ghcr.io/fluxcd/kustomize-controller:v0.32.0 ✔ notification-controller: deployment ready ► ghcr.io/fluxcd/notification-controller:v0.30.2 ✔ source-controller: deployment ready ► ghcr.io/fluxcd/source-controller:v0.33.0 ► checking crds ✔ alerts.notification.toolkit.fluxcd.io/v1beta2 ✔ buckets.source.toolkit.fluxcd.io/v1beta2 ✔ gitrepositories.source.toolkit.fluxcd.io/v1beta2 ✔ helmcharts.source.toolkit.fluxcd.io/v1beta2 ✔ helmreleases.helm.toolkit.fluxcd.io/v2beta1 ✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2 ✔ imagepolicies.image.toolkit.fluxcd.io/v1beta1 ✔ imagerepositories.image.toolkit.fluxcd.io/v1beta1 ✔ imageupdateautomations.image.toolkit.fluxcd.io/v1beta1 ✔ kustomizations.kustomize.toolkit.fluxcd.io/v1beta2 ✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2 ✔ providers.notification.toolkit.fluxcd.io/v1beta2 ✔ receivers.notification.toolkit.fluxcd.io/v1beta2 ✔ all checks passed

Git provider

No response

Container Registry provider

No response

Additional context

Thanks for your help!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

bug

opened by plockaby 1

GitHub Actions unreliable

Describe the bug

I'm trying to automate FluxCD Updates using the recommended workflow (https://github.com/fluxcd/flux2/tree/main/action#automate-flux-updates). Sadly this fails randomly multiple times a day.

Steps to reproduce

Setup workflow https://github.com/fluxcd/flux2/tree/main/action#automate-flux-updates
Monitor Success/Failure of GH Action

Expected behavior

Reliable execution of workflow

Screenshots and recordings

2023-01-01T10:08:13.0895617Z ##[group]Run fluxcd/flux2/[email protected]
2023-01-01T10:08:13.0895864Z with:
2023-01-01T10:08:13.0896033Z   arch: amd64
2023-01-01T10:08:13.0896219Z ##[endgroup]
2023-01-01T10:08:13.1231060Z ##[group]Run ARCH=amd64
2023-01-01T10:08:13.1231379Z [36;1mARCH=amd64[0m
2023-01-01T10:08:13.1231588Z [36;1mVERSION=[0m
2023-01-01T10:08:13.1231762Z [36;1m[0m
2023-01-01T10:08:13.1231959Z [36;1mif [ -z $VERSION ]; then[0m
2023-01-01T10:08:13.1232361Z [36;1m  VERSION=$(curl https://api.github.com/repos/fluxcd/flux2/releases/latest -sL | grep tag_name | sed -E 's/.*"([^"]+)".*/\1/' | cut -c 2-)[0m
2023-01-01T10:08:13.1232861Z [36;1mfi[0m
2023-01-01T10:08:13.1233034Z [36;1m[0m
2023-01-01T10:08:13.1233348Z [36;1mBIN_URL="https://github.com/fluxcd/flux2/releases/download/v${VERSION}/flux_${VERSION}_linux_${ARCH}.tar.gz"[0m
2023-01-01T10:08:13.1233704Z [36;1mcurl -sL ${BIN_URL} -o /tmp/flux.tar.gz[0m
2023-01-01T10:08:13.1233956Z [36;1mmkdir -p /tmp/flux[0m
2023-01-01T10:08:13.1234211Z [36;1mtar -C /tmp/flux/ -zxvf /tmp/flux.tar.gz[0m
2023-01-01T10:08:13.1292399Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2023-01-01T10:08:13.1292706Z ##[endgroup]
2023-01-01T10:08:13.2493808Z ##[error]Process completed with exit code 1.

OS / Distro

n/a

Flux version

n/a

Flux check

n/a

Git provider

No response

Container Registry provider

No response

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct

bug blocked-upstream

opened by fritterhoff 2

Flux CLI tool doesn't respect context namespace
Describe the bug

Say a Kubeconfig has the following block:

contexts: - context: cluster: cluster namespace: services user: user name: cluster current-context: cluster

When you run flux commands it will not target the namespace your context is currently using. It always targets flux-system unless the namespace flag is specified. For continuity sake between all kubernetes cli tools e.g. kubectl and helm the cli should use namespace context for CLI calls.

Steps to reproduce

Set your kubecontext to a namespace containing a helmrelease e.g.

namespace: services helmrelease: service

Run flux reconcile hr service

See this error ✗ helmreleases.helm.toolkit.fluxcd.io "service" not found

Run flux reconcile hr service --namespace service

It works

Expected behavior

Set your kubecontext to a namespace containing a helmrelease e.g.

namespace: services helmrelease: service

Run flux reconcile hr service it works

Screenshots and recordings

No response

OS / Distro

Fedora

Flux version

v0.38.2

Flux check

N/A

Git provider

No response

Container Registry provider

No response

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct
opened by sharkymcdongles 1
Pick latest build image always if no policy but filter tag given
Discussed in https://github.com/fluxcd/flux2/discussions/3265

^{Originally posted by marrip October 28, 2022} Hi,

I have a flux2 deployment running and want flux to automatically update the image I am running in the test environment. My images can be tagged with anything from <branch>-<sha> to semver tags. I created a ImagePolicy such as :

--- apiVersion: image.toolkit.fluxcd.io/v1beta1 kind: ImagePolicy metadata: name: test namespace: test spec: imageRepositoryRef: name: test namespace: test policy: alphabetical: order: asc

which is clearly not what I want as commit shas are random and I always want to last image built not the first on the list deployed into the cluster. Any pointers or ideas?
opened by abhijit838 0

Releases(v0.38.2)

v0.38.2(Dec 22, 2022)
Flux v0.38.2 is a patch release that comes with fixes for the Notification API v1beta1 to v1beta2 upgrade. In addition, this release improves the handling of the graceful shutdown for helm-controller. Users are encouraged to update Flux directly to v0.38.2 for the best experience.

Components changelog

notification-controller v0.30.2

helm-controller v0.28.1

CLI Changelog

PR #3437 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(32.73 KB)
flux_0.38.2_checksums.txt(1.17 KB)
flux_0.38.2_checksums.txt.pem(1.67 KB)
flux_0.38.2_checksums.txt.sig(96 bytes)
flux_0.38.2_darwin_amd64.tar.gz(18.45 MB)
flux_0.38.2_darwin_arm64.tar.gz(17.70 MB)
flux_0.38.2_linux_amd64.tar.gz(17.61 MB)
flux_0.38.2_linux_arm.tar.gz(16.75 MB)
flux_0.38.2_linux_arm64.tar.gz(15.99 MB)
flux_0.38.2_sbom.spdx.json(489.85 KB)
flux_0.38.2_source_code.tar.gz(373.43 KB)
flux_0.38.2_windows_386.zip(17.57 MB)
flux_0.38.2_windows_amd64.zip(17.78 MB)
flux_0.38.2_windows_arm64.zip(16.16 MB)
install.yaml(347.18 KB)
manifests.tar.gz(33.06 KB)
v0.38.1(Dec 21, 2022)
Flux v0.38.1 is a patch release that comes with fixes for the Notification API v1beta1 to v1beta2 upgrade. Users are encouraged to update Flux directly to v0.38.1 for the best experience.

Changelog

PR #3429 - @stefanprodan - Update CLI commands to Notification API v1beta2

PR #3428 - @fluxcdbot - Update notification-controller to v0.30.1

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(32.77 KB)
flux_0.38.1_checksums.txt(1.17 KB)
flux_0.38.1_checksums.txt.pem(1.67 KB)
flux_0.38.1_checksums.txt.sig(96 bytes)
flux_0.38.1_darwin_amd64.tar.gz(18.45 MB)
flux_0.38.1_darwin_arm64.tar.gz(17.70 MB)
flux_0.38.1_linux_amd64.tar.gz(17.61 MB)
flux_0.38.1_linux_arm.tar.gz(16.75 MB)
flux_0.38.1_linux_arm64.tar.gz(15.99 MB)
flux_0.38.1_sbom.spdx.json(489.85 KB)
flux_0.38.1_source_code.tar.gz(373.43 KB)
flux_0.38.1_windows_386.zip(17.57 MB)
flux_0.38.1_windows_amd64.zip(17.78 MB)
flux_0.38.1_windows_arm64.zip(16.16 MB)
install.yaml(347.24 KB)
manifests.tar.gz(33.06 KB)
v0.38.0(Dec 21, 2022)
Highlights

Flux v0.38.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Notification API v1beta2

This release graduates the Notification APIs to v1beta2. After upgrading the controllers on your clusters, you need to update the notification Custom Resources in Git by replacing notification.toolkit.fluxcd.io/v1beta1 with notification.toolkit.fluxcd.io/v1beta2 in all YAML manifests.

Breaking changes

The Alert.spec.summary has a max length of 255 characters.

The Provider.spec.address and Provider.spec.proxy have a max length of 2048 characters.

The Receiver.status.url was deprecated in favour of Receiver.status.webhookPath.

For more details about v1beta2 please see the notification-controller chagelog and the API spec documentation.

Features and improvements

Support for defining Kustomize components with Kustomization.spec.components.

Support for piping multi-doc YAMLs when publishing OCI artifacts with kustomize build . | flux push artifact --path=-.

Support for Gitea commit status updates with Provider.spec.type set to gitea.

Improve the memory usage of helm-controller by disabling the caching of Secret and ConfigMap resources.

Update the Helm SDK to v3.10.3 (fix for Helm CVEs).

All code references to libgit2 were removed, and the GitRepository.spec.gitImplementation field is no longer being honored.

Documentation improvements

The official example repository was refactored. The new version comes with the following improvements:

Make the example compatible with ARM64 Kubernetes clusters.

Add Weave GitOps Helm release to showcase the Flux UI.

Replace the ingress-nginx Bitnami chart with the official one that contains multi-arch container images.

Add cert-manager Helm release to showcase how to install CRDs and custom resources using dependsOn.

Add Let's Encrypt ClusterIssuer to showcase how to patch resources in production with Flux Kustomization.

Add the flux-system overlay to showcase how to configure Flux at bootstrap time.

Components changelog

source-controller v0.33.0

kustomize-controller v0.32.0

helm-controller v0.28.0

notification-controller v0.30.0

image-reflector-controller v0.23.1

image-automation-controller v0.28.0

CLI Changelog

PR #3427 - @hiddeco - Update dependencies

PR #3424 - @pjbgf - build: Revert sigstore/cosign-installer to v2.8.1

PR #3423 - @dependabot[bot] - Bump github/codeql-action from 2.1.36 to 2.1.37

PR #3422 - @dependabot[bot] - Bump goreleaser/goreleaser-action from 3.2.0 to 4.1.0

PR #3421 - @dependabot[bot] - Bump actions/setup-go from 3.4.0 to 3.5.0

PR #3420 - @dependabot[bot] - Bump actions/checkout from 3.1.0 to 3.2.0

PR #3418 - @somtochiama - Fix path on flux push

PR #3415 - @souleb - Fix dry-run still loading kubeconfig issue

PR #3413 - @aryan9600 - Update dependencies

PR #3408 - @souleb - Update fluxcd/pkg/kustomize dependency

PR #3404 - @stefanprodan - e2e: Fix Azure test suite

PR #3394 - @dependabot[bot] - Update sigstore/cosign-installer requirement to b6757d8360bb6b9803c38b68e8cb7442baaf7eb5

PR #3393 - @dependabot[bot] - Bump github/codeql-action from 2.1.35 to 2.1.36

PR #3389 - @somtochiama - Push/Build artifacts from stdin

PR #3377 - @aryan9600 - bootstrap: fallback to default known_hosts

PR #3372 - @dependabot[bot] - Bump peter-evans/create-pull-request from 4.2.2 to 4.2.3

PR #3371 - @dependabot[bot] - Bump snyk/actions from a8dd587d8a94f5663fa3d67d51abd0cc66aff244 to 1cc9026f51d822442cb4b872d8d7ead8cc69a018

PR #3370 - @dependabot[bot] - Bump actions/setup-go from 3.3.1 to 3.4.0

PR #3369 - @dependabot[bot] - Bump github/codeql-action from 2.1.33 to 2.1.35

PR #3360 - @fluxcdbot - Update toolkit components

PR #3352 - @dependabot[bot] - Bump peter-evans/create-pull-request from 4.2.0 to 4.2.2

PR #3350 - @stefanprodan - Set notification-controller container image to GHCR

PR #3345 - @stefanprodan - e2e: Refactor Azure test suite to use go-git

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(32.75 KB)
flux_0.38.0_checksums.txt(1.17 KB)
flux_0.38.0_checksums.txt.pem(1.67 KB)
flux_0.38.0_checksums.txt.sig(96 bytes)
flux_0.38.0_darwin_amd64.tar.gz(18.45 MB)
flux_0.38.0_darwin_arm64.tar.gz(17.70 MB)
flux_0.38.0_linux_amd64.tar.gz(17.61 MB)
flux_0.38.0_linux_arm.tar.gz(16.75 MB)
flux_0.38.0_linux_arm64.tar.gz(15.99 MB)
flux_0.38.0_sbom.spdx.json(489.85 KB)
flux_0.38.0_source_code.tar.gz(373.43 KB)
flux_0.38.0_windows_386.zip(17.57 MB)
flux_0.38.0_windows_amd64.zip(17.78 MB)
flux_0.38.0_windows_arm64.zip(16.16 MB)
install.yaml(347.24 KB)
manifests.tar.gz(33.06 KB)
v0.37.0(Nov 22, 2022)
Highlights

Flux v0.37.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes

Deprecation of gitImplementation

The interpretation of the gitImplementation field of GitRepository by source-controller and image-automation-controller has been deprecated, and will effectively always use go-git. This now supports all Git servers, including Azure DevOps and AWS CodeCommit, which previously were only supported by libgit2.

To opt-out from this behaviour, and get the controller to honour the field .spec.gitImplementation, start the controller with: --feature-gates=ForceGoGitImplementation=false.

For more information on this change, refer to the controllers's respective changelogs listed below.

Automatic force-push of ImageUpdateAutomation

Starting from this version, ImageUpdateAutomation objects with a .spec.PushBranch specified will have the push branch refreshed automatically via force push. To opt-out from this behaviour, start the controller with: --feature-gates=GitForcePushBranch=false.

Features and improvements

Support for bootstrapping Azure DevOps and AWS CodeCommit repositories using flux bootstrap git.

Support cloning of Git v2 protocol (Azure DevOps and AWS CodeCommit) for go-git Git provider.

Support force-pushing ImageUpdateAutomation repositories.

Allow a dry-run of flux build kustomization with --dry-run and --kustomization-file ./path/to/local/my-app.yaml. Using these flags, variable substitutions from Secrets and ConfigMaps are skipped, and no connection to the cluster is made.

Use signed OCI Helm chart for kube-prometheus-stack.

New documentation

Guide: AWS CodeCommit bootstrap

Guide: Azure DevOps bootstrap

Components changelog

source-controller v0.32.1

kustomize-controller v0.31.0

helm-controller v0.27.0

notification-controller v0.29.0

image-reflector-controller v0.23.0

image-automation-controller v0.27.0

CLI Changelog

PR #3339 - @hiddeco - Update dependencies

PR #3326 - @fluxcdbot - Update toolkit components

PR #3324 - @stefanprodan - Update kubectl and remove nsswitch.conf in flux-cli image

PR #3323 - @pjbgf - build: Pin GitHub Actions

PR #3317 - @souleb - Add a dry-run mode to flux build kustomization

PR #3303 - @stefanprodan - monitoring: Use kube-prometheus-stack signed OCI Helm chart

PR #3299 - @aryan9600 - Refactor bootstrap process to use fluxcd/pkg/git

PR #3294 - @phillebaba - Aggregate errors in uninstall functions

PR #3288 - @dependabot[bot] - Bump hashicorp/setup-terraform from 2.0.2 to 2.0.3

PR #3281 - @stefanprodan - Refactor ARM64 e2e test suite

PR #3269 - @dependabot[bot] - Bump actions/setup-go from 2 to 3

PR #3249 - @phillebaba - Remove file reading from bootstrap package

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(31.45 KB)
flux_0.37.0_checksums.txt(1.17 KB)
flux_0.37.0_checksums.txt.pem(1.67 KB)
flux_0.37.0_checksums.txt.sig(96 bytes)
flux_0.37.0_darwin_amd64.tar.gz(18.59 MB)
flux_0.37.0_darwin_arm64.tar.gz(17.83 MB)
flux_0.37.0_linux_amd64.tar.gz(17.76 MB)
flux_0.37.0_linux_arm.tar.gz(16.98 MB)
flux_0.37.0_linux_arm64.tar.gz(16.12 MB)
flux_0.37.0_sbom.spdx.json(455.28 KB)
flux_0.37.0_source_code.tar.gz(363.13 KB)
flux_0.37.0_windows_386.zip(17.69 MB)
flux_0.37.0_windows_amd64.zip(17.93 MB)
flux_0.37.0_windows_arm64.zip(16.28 MB)
install.yaml(318.01 KB)
manifests.tar.gz(31.26 KB)
v0.36.0(Oct 24, 2022)
Highlights

Flux v0.36.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Features and improvements

Verify OCI Helm charts signed by Cosign (including keyless) with HelmChart.spec.verify.

Allow publishing a single YAML file to OCI with flux push artifact <URL> --path=deploy/install.yaml.

Detect changes to local files before pushing to OCI with flux diff artifact <URL> --path=<local files>.

New Alert Provider type named generic-hmac for authenticating the webhook requests coming from notification-controller.

The Kustomization.status.conditions have been aligned with Kubernetes standard conditions and kstatus.

The kustomize-controller memory usage was reduced by 90% when performing artifact operations.

New documentation

Guide: How to deploy Flagger with Flux using signed Helm charts and OCI artifacts

FAQ: Should I be using Kustomize remote bases?

FAQ: Should I be using Kustomize Helm chart plugin?

Components changelog

source-controller v0.31.0

kustomize-controller v0.30.0

helm-controller v0.26.0

notification-controller v0.28.0

image-reflector-controller v0.22.1

image-automation-controller v0.26.1

CLI Changelog

PR #3242 - @stefanprodan - Update dependencies

PR #3237 - @phillebaba - Move bootstrap package from internal to pkg

PR #3236 - @stefanprodan - ci: Refactor GitHub workflows

PR #3232 - @eddie-knight - Additional workflow permissions tweaks

PR #3231 - @eddie-knight - Adjusted workflow permissions

PR #3229 - @stefanprodan - RFC-0002: Add Cosign verification for Helm OCI charts

PR #3224 - @developer-guy - Add diff artifact command

PR #3220 - @stefanprodan - Only run e2e tests for Dependabot PRs

PR #3219 - @dependabot[bot] - Bump github/codeql-action from 1 to 2

PR #3218 - @dependabot[bot] - Bump peter-evans/create-pull-request from 3 to 4

PR #3217 - @dependabot[bot] - Bump hashicorp/setup-terraform from 1 to 2.0.2

PR #3216 - @stefanprodan - Enable Dependabot for GitHub Actions

PR #3214 - @eddie-knight - Added ArtifactHub badge

PR #3213 - @stefanprodan - Add FOSSA license scanning badge

PR #3198 - @phillebaba - Add nop logger

PR #3197 - @phillebaba - Move uninstall code to pkg

PR #3190 - @developer-guy - Accept a file path as input for flux build|push artifact

PR #3187 - @fluxcdbot - Update toolkit components

PR #3174 - @phillebaba - Update libgit2 version in Azure e2e tests

PR #3162 - @somtochiama - Update golden file for get source oci

PR #3161 - @stefanprodan - Update RFC-0003 implementation history

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(37.25 KB)
flux_0.36.0_checksums.txt(1.17 KB)
flux_0.36.0_checksums.txt.pem(1.68 KB)
flux_0.36.0_checksums.txt.sig(96 bytes)
flux_0.36.0_darwin_amd64.tar.gz(17.81 MB)
flux_0.36.0_darwin_arm64.tar.gz(17.06 MB)
flux_0.36.0_linux_amd64.tar.gz(17.01 MB)
flux_0.36.0_linux_arm.tar.gz(16.23 MB)
flux_0.36.0_linux_arm64.tar.gz(15.42 MB)
flux_0.36.0_sbom.spdx.json(409.22 KB)
flux_0.36.0_source_code.tar.gz(372.86 KB)
flux_0.36.0_windows_386.zip(16.93 MB)
flux_0.36.0_windows_amd64.zip(17.17 MB)
flux_0.36.0_windows_arm64.zip(15.58 MB)
install.yaml(377.49 KB)
manifests.tar.gz(34.11 KB)
v0.35.0(Sep 29, 2022)
Highlights

Flux v0.35.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes

Strict validation rules have been put in place for API fields which define a time duration, such as .spec.interval. Effectively, this means values without a time unit (e.g. ms, s, m, h) will now be rejected by the API server.

Features and improvements

Verify OCI artifacts signed by Cosign (including keyless) with OCIRepository.spec.verify.

Allow pulling Helm charts dependencies from HTTPS repositories with mixed self-signed TLS and public CAs.

Allow pulling Helm charts from OCI artifacts stored at the root of AWS ECR.

Allow running bootstrap for insecure HTTP Git servers with flux bootstrap git --allow-insecure-http --token-auth.

Improve health checking for global objects such as ClusterClass, GatewayClass, StorageClass, etc.

The controllers and the Flux CLI are now built with Go 1.19.

For more information on OCI and Cosign support please see the Flux documentation.

Components changelog

source-controller v0.30.0

kustomize-controller v0.29.0

helm-controller v0.25.0

notification-controller v0.27.0

image-reflector-controller v0.22.0

image-automation-controller v0.26.0

CLI Changelog

PR #3154 - @stefanprodan - [RFC-0003] Add Cosign keyless specification

PR #3153 - @stefanprodan - Build with Go 1.19

PR #3149 - @fluxcdbot - Update toolkit components

PR #3145 - @stefanprodan - Add component label for controllers and their CRDs

PR #3117 - @carlosonunez-vmw - Maintain original scheme when using --token-auth

PR #3098 - @Santosh1176 - [Grafana] Use container_memory_working_set_bytes to report memory consumption

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(34.12 KB)
flux_0.35.0_checksums.txt(1.17 KB)
flux_0.35.0_checksums.txt.pem(1.68 KB)
flux_0.35.0_checksums.txt.sig(96 bytes)
flux_0.35.0_darwin_amd64.tar.gz(17.76 MB)
flux_0.35.0_darwin_arm64.tar.gz(17.02 MB)
flux_0.35.0_linux_amd64.tar.gz(16.96 MB)
flux_0.35.0_linux_arm.tar.gz(16.19 MB)
flux_0.35.0_linux_arm64.tar.gz(15.39 MB)
flux_0.35.0_sbom.spdx.json(390.46 KB)
flux_0.35.0_source_code.tar.gz(387.21 KB)
flux_0.35.0_windows_386.zip(16.88 MB)
flux_0.35.0_windows_amd64.zip(17.12 MB)
flux_0.35.0_windows_arm64.zip(15.53 MB)
install.yaml(371.34 KB)
manifests.tar.gz(33.21 KB)
v0.34.0(Sep 12, 2022)
Highlights

Flux v0.34.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes

The Flux controller logs have been aligned with the Kubernetes structured logging. For more details on the new logging structure please see: fluxcd/flux2#3051.

Features and improvements

OCIRepository.spec.insecure Allow pulling artifacts from an in-cluster Docker Registry over plain HTTP.

Allow defining OCI sources for non-TLS container registries with flux create source oci --insecure.

Enable contextual login when publishing OCI artifacts from a Cloud VM using flux push artifact --provider=aws|azure|gcp.

Prioritise static credentials over OIDC providers when pulling OCI artifacts from container registries on multi-tenant cluster.

Reconcile Kubernetes Class types (ClusterClass, GatewayClass, StorageClass, etc) in a dedicated stage before any other custom resources like Clusters, Gateways, Volumes, etc.

When multiple SOPS providers are available, run the offline decryption methods first to avoid failures due to KMS unavailability.

Add finalizers to the notification API to properly record the reconciliation metrics for deleted resources.

Publish the Flux install manifests as OCI artifacts on GitHub and DockerHub container registries under fluxcd/flux-manifests.

Components Changelog

source-controller v0.29.0

kustomize-controller v0.28.0

helm-controller v0.24.0

notification-controller v0.26.0

image-reflector-controller v0.21.0

image-automation-controller v0.25.0

CLI Changelog

PR #3097 - @stefanprodan - Add --insecure flag to flux create source oci

PR #3091 - @fluxcdbot - Update toolkit components

PR #3088 - @stefanprodan - Publish the install manifests to GHCR and DockerHub as OCI artifacts

PR #3087 - @somtochiama - Remove finalizers for notification CRs on uninstall

PR #3085 - @souleb - [bootstrap] Make sure we reconcile with the right reconciliation method

PR #3082 - @stefanprodan - Remove finalizers for OCI repositories on uninstall

PR #3079 - @adrien-f - Support autologin when pushing OCI artifacts

PR #3073 - @acondrat - Filter out non-running pods in Prometheus

PR #3063 - @somtochiama - Update flux logs to accomodate the new format

PR #3053 - @dholbach - Revert "Fix broken "edit this page" links in Flux CLI section"

PR #3052 - @dholbach - update to new doc links structure

PR #3050 - @stefanprodan - Status update for RFC-0002 and RFC-0003

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(34.19 KB)
flux_0.34.0_checksums.txt(1.17 KB)
flux_0.34.0_checksums.txt.pem(1.67 KB)
flux_0.34.0_checksums.txt.sig(96 bytes)
flux_0.34.0_darwin_amd64.tar.gz(17.63 MB)
flux_0.34.0_darwin_arm64.tar.gz(16.94 MB)
flux_0.34.0_linux_amd64.tar.gz(16.84 MB)
flux_0.34.0_linux_arm.tar.gz(16.08 MB)
flux_0.34.0_linux_arm64.tar.gz(15.31 MB)
flux_0.34.0_sbom.spdx.json(387.61 KB)
flux_0.34.0_source_code.tar.gz(386.76 KB)
flux_0.34.0_windows_386.zip(16.72 MB)
flux_0.34.0_windows_amd64.zip(16.95 MB)
flux_0.34.0_windows_arm64.zip(15.43 MB)
install.yaml(368.53 KB)
manifests.tar.gz(32.40 KB)
v0.33.0(Aug 29, 2022)
Highlights

Flux v0.33.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Features and improvements

HelmRepository.spec.provider Enable contextual login to container registries when pulling Helm charts from Amazon Elastic Container Registry, Azure Container Registry and Google Artifact Registry.

OCIRepository.spec.layerSelector Select which layer contains the Kubernetes configs by specifying a matching OCI media type.

Bucket.spec.secretRef Authenticate to Azure Blob storage using SAS tokens.

Allow filtering OCI artifacts by semver and regex when listing artifact with flux list artifacts.

Allow excluding local files and directories when building and publishing artifacts with flux push artifact.

Mitigate denial-of-service on multi-tenant clusters by automatically recovering from panics encountered during reconciliation.

Update controllers to Kubernetes v1.25.0, Kustomize v4.5.7 and Helm v3.9.4.

New documentation

Secrets Management

Contextual Authorization

Components changelog

source-controller v0.27.0 v0.28.0

kustomize-controller v0.27.1

helm-controller v0.23.1

notification-controller v0.25.2

image-reflector-controller v0.20.1

image-automation-controller v0.24.2

CLI Changelog

PR #3049 - @stefanprodan - Update Kubernetes dependencies to v1.25.0

PR #3034 - @snebel29 - Fix broken "edit this page" links in Flux CLI section

PR #3028 - @snebel29 - Update tests/azure github.com/hashicorp/terraform-exec to v0.16.1

PR #3025 - @stefanprodan - [RFC-0002] Add auth specification for Helm OCI

PR #3024 - @stefanprodan - Add version validation to install commands

PR #3019 - @somtochiama - Improve error message in get cmd

PR #3014 - @stefanprodan - [RFC-0003] Select layer by OCI media type

PR #2999 - @fluxcdbot - Update toolkit components

PR #2998 - @somtochiama - Add --filter-semver and --filter-regex flags to list artifacts

PR #2997 - @stefanprodan - Use ghcr.io in the static manifests

PR #2996 - @stefanprodan - Update dependencies

PR #2995 - @stefanprodan - Add --ignore-paths arg to flux build|push artifact

PR #2979 - @stefanprodan - Status update for RFC-0002 and RFC-0003

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(34.16 KB)
flux_0.33.0_checksums.txt(1.17 KB)
flux_0.33.0_checksums.txt.pem(1.68 KB)
flux_0.33.0_checksums.txt.sig(96 bytes)
flux_0.33.0_darwin_amd64.tar.gz(16.41 MB)
flux_0.33.0_darwin_arm64.tar.gz(15.77 MB)
flux_0.33.0_linux_amd64.tar.gz(15.66 MB)
flux_0.33.0_linux_arm.tar.gz(14.90 MB)
flux_0.33.0_linux_arm64.tar.gz(14.24 MB)
flux_0.33.0_sbom.spdx.json(381.11 KB)
flux_0.33.0_source_code.tar.gz(393.97 KB)
flux_0.33.0_windows_386.zip(15.60 MB)
flux_0.33.0_windows_amd64.zip(15.77 MB)
flux_0.33.0_windows_arm64.zip(14.34 MB)
install.yaml(368.24 KB)
manifests.tar.gz(32.36 KB)
v0.32.0(Aug 11, 2022)
Highlights

Flux v0.32.0 comes with support for distributing Kubernetes manifests, Kustomize overlays and Terraform code as OCI artifacts. For more information please see the Flux OCI documentation.

New features

New Flux CLI commands flux push|pull|tag artifact for publishing OCI Artifacts to container registries.

New source type OCIRepository for fetching OCI artifacts from container registries.

Resolve Helm dependencies from OCI for charts defined in Git.

Components changelog

source-controller v0.26.0 v0.26.1

kustomize-controller v0.27.0

notification-controller v0.25.0 v0.25.1

image-reflector-controller v0.20.0

image-automation-controller v0.24.1

CLI Changelog

PR #2966 - @fluxcdbot - Update toolkit components

PR #2964 - @pjbgf - Add validation to namespace flag

PR #2955 - @somtochiama - fix log filter and add tests for flux logs

PR #2951 - @stefanprodan - [RFC-0003] Add the provider field for OIDC auth

PR #2940 - @hiddeco - AUR: further solve .SRCINFO issues

PR #2937 - @hiddeco - AUR: ensure pkgname is bottom entry in .SRCINFO

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(35.63 KB)
flux_0.32.0_checksums.txt(1.17 KB)
flux_0.32.0_checksums.txt.pem(1.68 KB)
flux_0.32.0_checksums.txt.sig(96 bytes)
flux_0.32.0_darwin_amd64.tar.gz(16.16 MB)
flux_0.32.0_darwin_arm64.tar.gz(15.53 MB)
flux_0.32.0_linux_amd64.tar.gz(15.41 MB)
flux_0.32.0_linux_arm.tar.gz(14.64 MB)
flux_0.32.0_linux_arm64.tar.gz(14.02 MB)
flux_0.32.0_sbom.spdx.json(393.77 KB)
flux_0.32.0_source_code.tar.gz(406.31 KB)
flux_0.32.0_windows_386.zip(15.33 MB)
flux_0.32.0_windows_amd64.zip(15.52 MB)
flux_0.32.0_windows_arm64.zip(14.11 MB)
install.yaml(365.69 KB)
manifests.tar.gz(32.01 KB)
v0.31.5(Jul 27, 2022)
Highlights

Flux v0.31.5 is a patch release that comes with fixes. Users are encouraged to upgrade for the best experience.

Fixes

Fix ImageRepository public repository scan for unconfigured provider registries

Improvements

Improve Helm OCI Chart to work with registries that don't support listing tags

Component changelog

source-controller v0.25.11

image-reflector-controller v0.19.4

CLI Changelog

PR #2932 - @fluxcdbot - Update toolkit components

PR #2917 - @morancj - SRCINFO: fix path

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(34.29 KB)
flux_0.31.5_checksums.txt(1.17 KB)
flux_0.31.5_checksums.txt.pem(1.67 KB)
flux_0.31.5_checksums.txt.sig(96 bytes)
flux_0.31.5_darwin_amd64.tar.gz(15.67 MB)
flux_0.31.5_darwin_arm64.tar.gz(15.05 MB)
flux_0.31.5_linux_amd64.tar.gz(14.94 MB)
flux_0.31.5_linux_arm.tar.gz(14.18 MB)
flux_0.31.5_linux_arm64.tar.gz(13.58 MB)
flux_0.31.5_sbom.spdx.json(375.37 KB)
flux_0.31.5_source_code.tar.gz(378.38 KB)
flux_0.31.5_windows_386.zip(14.84 MB)
flux_0.31.5_windows_amd64.zip(15.05 MB)
flux_0.31.5_windows_arm64.zip(13.69 MB)
install.yaml(351.43 KB)
manifests.tar.gz(30.81 KB)
v0.31.4(Jul 18, 2022)
Highlights

Flux v0.31.4 is a patch release that comes with fixes. Users are encouraged to upgrade for the best experience.

Fixes

Fix SIGSEGV when resolving charts dependencies.

Fix Panic when no artifact in source.

decryptor: recover from SOPS store panic.

Fix spelling mistake in azure/exchanger.go.

Improvements

Retry downloading artifacts on not found errors.

Components changelog

source-controller v0.25.10

kustomize-controller v0.26.3

notification-controller v0.24.1

helm-controller v0.22.2

image-automation-controller v0.23.5

image-reflector-controller v0.19.3

CLI Changelog

PR #2905 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(33.68 KB)
flux_0.31.4_checksums.txt(1.17 KB)
flux_0.31.4_checksums.txt.pem(1.67 KB)
flux_0.31.4_checksums.txt.sig(96 bytes)
flux_0.31.4_darwin_amd64.tar.gz(15.67 MB)
flux_0.31.4_darwin_arm64.tar.gz(15.05 MB)
flux_0.31.4_linux_amd64.tar.gz(14.94 MB)
flux_0.31.4_linux_arm.tar.gz(14.18 MB)
flux_0.31.4_linux_arm64.tar.gz(13.58 MB)
flux_0.31.4_sbom.spdx.json(375.36 KB)
flux_0.31.4_source_code.tar.gz(378.38 KB)
flux_0.31.4_windows_386.zip(14.84 MB)
flux_0.31.4_windows_amd64.zip(15.05 MB)
flux_0.31.4_windows_arm64.zip(13.69 MB)
install.yaml(351.43 KB)
manifests.tar.gz(30.81 KB)
v0.31.3(Jun 29, 2022)
Highlights

Flux v0.31.3 is a patch release that comes with fixes. Users are encouraged to upgrade for the best experience.

Fixes

Fix for Helm OCI authentication where the credentials were cached instead of being reloaded at each reconciliation

Fix for health checking Kubernetes Jobs when impersonating a service account

Components changelog

source-controller v0.25.9

kustomize-controller v0.26.2

CLI Changelog

PR #2881 - @fluxcdbot - Update toolkit components

PR #2877 - @sympatheticmoose - Add the --branch arg to the basic auth example

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(35.92 KB)
flux_0.31.3_checksums.txt(1.17 KB)
flux_0.31.3_checksums.txt.pem(1.68 KB)
flux_0.31.3_checksums.txt.sig(96 bytes)
flux_0.31.3_darwin_amd64.tar.gz(15.67 MB)
flux_0.31.3_darwin_arm64.tar.gz(15.05 MB)
flux_0.31.3_linux_amd64.tar.gz(14.94 MB)
flux_0.31.3_linux_arm.tar.gz(14.18 MB)
flux_0.31.3_linux_arm64.tar.gz(13.58 MB)
flux_0.31.3_sbom.spdx.json(375.04 KB)
flux_0.31.3_source_code.tar.gz(374.68 KB)
flux_0.31.3_windows_386.zip(14.84 MB)
flux_0.31.3_windows_amd64.zip(15.05 MB)
flux_0.31.3_windows_arm64.zip(13.69 MB)
install.yaml(351.43 KB)
manifests.tar.gz(30.81 KB)
v0.31.2(Jun 24, 2022)
Highlights

Flux v0.31.2 is a patch release that comes with fixes and small improvements. Users are encouraged to upgrade for the best experience.

Fixes and improvements

Fix SSH connection leaks when using libgit2 managed transport

Improve the libgit2 error messages when the known hosts check fails

Fix authentication for BitBucket server when using libgit2 managed transport

Fix flux logs when running Flux inside a service mesh

Fix flux reconcile source helm when using Helm OCI

Accept multiple values for flux create hr --values-from

List the Flux CRDs and assert their statuses when running flux check

Add finalizers to ImageRepository, ImagePolicy and ImageUpdateAutomation resources to properly record the metrics for deleted resources

Components changelog

source-controller v0.25.8 v0.25.7 v0.25.6

image-reflector-controller v0.19.2

image-automation-controller v0.23.4 v0.23.3

CLI Changelog

PR #2867 - @stefanprodan - Remove image finalizers on uninstall

PR #2862 - @bplasmeijer - Put the dashboard configmap in the right namespace for monitoring

PR #2859 - @somtochiama - Return different success message for oci type - reconcile_source_helm

PR #2844 - @hiddeco - logs: select manager container when multiple exist

PR #2839 - @fluxcdbot - Update toolkit components

PR #2829 - @somtochiama - Accept multiple values for flux create hr --values-from

PR #2823 - @stefanprodan - Add CRDs to flux check command

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(35.91 KB)
flux_0.31.2_checksums.txt(1.17 KB)
flux_0.31.2_checksums.txt.pem(1.67 KB)
flux_0.31.2_checksums.txt.sig(96 bytes)
flux_0.31.2_darwin_amd64.tar.gz(15.67 MB)
flux_0.31.2_darwin_arm64.tar.gz(15.06 MB)
flux_0.31.2_linux_amd64.tar.gz(14.94 MB)
flux_0.31.2_linux_arm.tar.gz(14.18 MB)
flux_0.31.2_linux_arm64.tar.gz(13.58 MB)
flux_0.31.2_sbom.spdx.json(375.04 KB)
flux_0.31.2_source_code.tar.gz(374.47 KB)
flux_0.31.2_windows_386.zip(14.84 MB)
flux_0.31.2_windows_amd64.zip(15.05 MB)
flux_0.31.2_windows_arm64.zip(13.69 MB)
install.yaml(351.43 KB)
manifests.tar.gz(30.81 KB)
v0.31.1(Jun 8, 2022)
Highlights

Flux v0.31.1 is a patch release that comes with important fixes and documentation improvements. Users are encouraged to upgrade for the best experience.

Fixes

Fix semver sorting for Helm OCI charts (source-controller)

Fix service account impersonation when using target namespace (helm-controller)

Validate that the image name does not contain tags (image-reflector-controller)

Fix libgit2 SSH host key verification (source-controller & image-automation-controller)

Fix authentication when using Gitlab via HTTP/S (source-controller & image-automation-controller)

Documentation improvements

Explain how to generate image pull secrets from SOPS encrypted .dockerconfigjson files

Document all controller flags and their defaults

source-controller options

kustomize-controller options

helm-controller options

notification-controller options

image-automation-controller options

image-reflector-controller options

Components changelog

source-controller v0.25.5 v0.25.4

kustomize-controller v0.26.1

helm-controller v0.22.1

image-reflector-controller v0.19.1

image-automation-controller v0.23.2 v0.23.1

CLI Changelog

PR #2820 - @stefanprodan - Update dependencies

PR #2814 - @fluxcdbot - Update toolkit components

PR #2811 - @stefanprodan - [RFC-0002] Update status and implementation history

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(33.45 KB)
flux_0.31.1_checksums.txt(1.17 KB)
flux_0.31.1_checksums.txt.pem(1.67 KB)
flux_0.31.1_checksums.txt.sig(96 bytes)
flux_0.31.1_darwin_amd64.tar.gz(15.67 MB)
flux_0.31.1_darwin_arm64.tar.gz(15.05 MB)
flux_0.31.1_linux_amd64.tar.gz(14.94 MB)
flux_0.31.1_linux_arm.tar.gz(14.18 MB)
flux_0.31.1_linux_arm64.tar.gz(13.58 MB)
flux_0.31.1_sbom.spdx.json(375.69 KB)
flux_0.31.1_source_code.tar.gz(374.25 KB)
flux_0.31.1_windows_386.zip(14.84 MB)
flux_0.31.1_windows_amd64.zip(15.05 MB)
flux_0.31.1_windows_arm64.zip(13.68 MB)
install.yaml(351.43 KB)
manifests.tar.gz(30.81 KB)
v0.31.0(Jun 6, 2022)
Highlights

Flux v0.31.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes

Flux is no longer compatible with kubeconfigs using client.authentication.k8s.io/v1alpha1, this version was deprecated and removed in Kubernetes 1.24. Please follow these instructions on how to update kubeconfig to client.authentication.k8s.io/v1beta1.

New features

Pull Helm charts from container registries by configuring Helm repositories with type: oci. For more information please see the Helm OCI documentation.

Trigger GitHub Actions workflows from Flux by configuring alerting providers with type: githubdispatch. For more information please see the GitHub dispatch provider documentation.

New guides

Promote Flux Helm Releases with GitHub Actions.

Using Flux on GKE with Google Cloud Source Repositories.

Monitoring Flux logs with Loki and Grafana.

New improvements and fixes

Starting with this version, all Flux controllers conform to the Kubernetes API Priority and Fairness.

Add support for configuring the authentication to AWS KMS, Azure Key Vault and Google Cloud KMS on multi-tenant clusters.

The Git reconciliation has been made more efficient by adding support for no-op clones that should reduce the outbound traffic substantially.

The libgit2 managed transport feature has been enabled by default to improve the Azure DevOps and AWS CodeCommit Git operations.

Fix an issue where the token used for Helm operations would go stale if it was provided using a Bound Service Account Token Volume.

Update the controllers and CLI dependencies to Kubernetes v1.24, Kustomize v4.5.5 and Helm v3.9.0.

Components changelog

source-controller v0.25.0 v0.25.1 v0.25.3

kustomize-controller v0.26.0

helm-controller v0.22.0

notification-controller v0.24.0

image-reflector-controller v0.19.0

image-automation-controller v0.23.0

CLI Changelog

PR #2809 - @fluxcdbot - Update source-controller to v0.25.3

PR #2807 - @stefanprodan - Update dependencies

PR #2806 - @stefanprodan - monitoring: Add Grafana Loki HR and Flux logs dashboard

PR #2802 - @stefanprodan - Add --kubeconfig-secret-ref to flux create ks|hr

PR #2801 - @stefanprodan - e2e: Update ARM64 runners to Kubernetes 1.24

PR #2796 - @fluxcdbot - Update toolkit components

PR #2792 - @SomtochiAma - Handle multi-doc yaml for flux build

PR #2787 - @vipulnewaskar7 - Add --allow-insecure-http to bootstrap git

PR #2782 - @stefanprodan - Refactor Flux Prometheus monitoring stack

PR #2781 - @makkes - Add OCI support to create source helm

PR #2778 - @stefanprodan - Update go-git-providers to v0.6.0

PR #2775 - @fluxcdbot - Update toolkit components

PR #2773 - @stefanprodan - Update dependencies

PR #2769 - @stefanprodan - Update Go to 1.18 in CI

PR #2767 - @takirala - Add --ignore-paths flag to flux create source (git|bucket)

PR #2764 - @hiddeco - Ensure proper FS root is set while bootstrapping

PR #2748 - @makkes - fix e2e tests

PR #2747 - @dholbach - Move MAINTAINERS to f/community

PR #2727 - @cr1cr1 - grafana: display exported ns, slight resizing, default sorting by state

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(33.45 KB)
flux_0.31.0_checksums.txt(1.17 KB)
flux_0.31.0_checksums.txt.pem(1.67 KB)
flux_0.31.0_checksums.txt.sig(96 bytes)
flux_0.31.0_darwin_amd64.tar.gz(15.67 MB)
flux_0.31.0_darwin_arm64.tar.gz(15.05 MB)
flux_0.31.0_linux_amd64.tar.gz(14.94 MB)
flux_0.31.0_linux_arm.tar.gz(14.18 MB)
flux_0.31.0_linux_arm64.tar.gz(13.58 MB)
flux_0.31.0_sbom.spdx.json(375.69 KB)
flux_0.31.0_source_code.tar.gz(374.41 KB)
flux_0.31.0_windows_386.zip(14.84 MB)
flux_0.31.0_windows_amd64.zip(15.05 MB)
flux_0.31.0_windows_arm64.zip(13.68 MB)
install.yaml(351.43 KB)
manifests.tar.gz(30.80 KB)
v0.30.2(May 4, 2022)
Flux v0.30.2 is a patch release with further patches around working with the macOS file-system.

Note that v0.29.0 included breaking changes, and v0.30.0 new features.

CLI Changelog

PR #2703 - @aryan9600 - Modify tmp dir generation to be absolute on all OSes

PR #2701 - @stefanprodan - Grant service account read-only access to controllers

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(34.27 KB)
flux_0.30.2_checksums.txt(1.17 KB)
flux_0.30.2_checksums.txt.pem(1.43 KB)
flux_0.30.2_checksums.txt.sig(96 bytes)
flux_0.30.2_darwin_amd64.tar.gz(14.93 MB)
flux_0.30.2_darwin_arm64.tar.gz(14.86 MB)
flux_0.30.2_linux_amd64.tar.gz(14.22 MB)
flux_0.30.2_linux_arm.tar.gz(13.37 MB)
flux_0.30.2_linux_arm64.tar.gz(12.98 MB)
flux_0.30.2_sbom.spdx.json(368.99 KB)
flux_0.30.2_source_code.tar.gz(391.34 KB)
flux_0.30.2_windows_386.zip(14.16 MB)
flux_0.30.2_windows_amd64.zip(14.41 MB)
flux_0.30.2_windows_arm64.zip(13.17 MB)
install.yaml(350.24 KB)
manifests.tar.gz(30.52 KB)
v0.30.1(May 4, 2022)
Flux v0.30.1 is a patch release fixing a regression bug introduced in v0.30.0, which prevented macOS users from upgrading Flux using bootstrap due to FS security constraints.

Note that v0.29.0 included breaking changes, and v0.30.0 new features.

CLI Changelog

PR #2700 - @stefanprodan - MacOS: fix bootstrap manifest generation

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(34.26 KB)
flux_0.30.1_checksums.txt(1.17 KB)
flux_0.30.1_checksums.txt.pem(1.43 KB)
flux_0.30.1_checksums.txt.sig(96 bytes)
flux_0.30.1_darwin_amd64.tar.gz(14.93 MB)
flux_0.30.1_darwin_arm64.tar.gz(14.86 MB)
flux_0.30.1_linux_amd64.tar.gz(14.22 MB)
flux_0.30.1_linux_arm.tar.gz(13.37 MB)
flux_0.30.1_linux_arm64.tar.gz(12.98 MB)
flux_0.30.1_sbom.spdx.json(368.68 KB)
flux_0.30.1_source_code.tar.gz(391.04 KB)
flux_0.30.1_windows_386.zip(14.16 MB)
flux_0.30.1_windows_amd64.zip(14.41 MB)
flux_0.30.1_windows_arm64.zip(13.17 MB)
install.yaml(350.14 KB)
manifests.tar.gz(30.50 KB)
v0.30.0(May 3, 2022)
Flux v0.30.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Note that v0.29.0 included breaking changes.

Features and improvements

Support for disabling remote bases in Kustomize overlays

This release adds support to the kustomize-controller for disallowing remote bases in Kustomize overlays using --no-remote-bases=true (default: false). When this flag is enabled on the controller, all resources must refer to local files included in the Source Artifact, meaning only the Flux Sources can affect the cluster-state. Users are advised to enable it on production systems for security and performance reasons.

Support for defining a KubeConfig Secret data key

Both Kustomization and HelmRelease resources do now accept a .spec.kubeConfig.SecretRef.key definition. When the value is specified, the KubeConfig JSON is retrieved from this data key in the referred Secret, instead of the defaults (value or value.yaml).

Support for defining a ServiceAccountName in ImageRepository objects

The ImageRepository object does now accept a .spec.serviceAccountName definition. When specified, the image pull secrets attached to the ServiceAccount are used to authenticate towards the registry.

Components Changelog

kustomize-controller to v0.25.0

helm-controller to v0.21.0

image-reflector-controller to v0.18.0

source-controller to v0.24.4

notification-controller to v0.23.5

image-automation-controller to v0.22.1

CLI Changelog

PR #2651 - @hiddeco - kustomize: use FS from fluxcd/pkg

PR #2698 - @hiddeco - Update dependencies

PR #2695 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(34.26 KB)
flux_0.30.0_checksums.txt(1.17 KB)
flux_0.30.0_checksums.txt.pem(1.43 KB)
flux_0.30.0_checksums.txt.sig(96 bytes)
flux_0.30.0_darwin_amd64.tar.gz(14.93 MB)
flux_0.30.0_darwin_arm64.tar.gz(14.86 MB)
flux_0.30.0_linux_amd64.tar.gz(14.22 MB)
flux_0.30.0_linux_arm.tar.gz(13.37 MB)
flux_0.30.0_linux_arm64.tar.gz(12.98 MB)
flux_0.30.0_sbom.spdx.json(368.68 KB)
flux_0.30.0_source_code.tar.gz(391.08 KB)
flux_0.30.0_windows_386.zip(14.16 MB)
flux_0.30.0_windows_amd64.zip(14.41 MB)
flux_0.30.0_windows_arm64.zip(13.17 MB)
install.yaml(350.14 KB)
manifests.tar.gz(30.50 KB)
v0.29.5(Apr 28, 2022)
Flux v0.29.5 is patch release which improves the Condition handling of HelmRepository resources, and handling of file formats while decrypting Secret generator entries with SOPS to ensure encrypted files in format A can be decrypted to target format B.

In addition, we now recover from Kustomize build panics to guarantee continuity of operations when running into invalid object data.

Note that v0.29.0 includes breaking changes.

Components Changelog

source-controller to v0.24.3

kustomize-controller to v0.24.4

CLI Changelog

PR #2686 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(34.13 KB)
flux_0.29.5_checksums.txt(1.17 KB)
flux_0.29.5_checksums.txt.pem(1.43 KB)
flux_0.29.5_checksums.txt.sig(96 bytes)
flux_0.29.5_darwin_amd64.tar.gz(14.93 MB)
flux_0.29.5_darwin_arm64.tar.gz(14.84 MB)
flux_0.29.5_linux_amd64.tar.gz(14.21 MB)
flux_0.29.5_linux_arm.tar.gz(13.36 MB)
flux_0.29.5_linux_arm64.tar.gz(12.97 MB)
flux_0.29.5_sbom.spdx.json(368.68 KB)
flux_0.29.5_source_code.tar.gz(390.36 KB)
flux_0.29.5_windows_386.zip(14.15 MB)
flux_0.29.5_windows_amd64.zip(14.41 MB)
flux_0.29.5_windows_arm64.zip(13.16 MB)
install.yaml(349.39 KB)
manifests.tar.gz(30.28 KB)
v0.29.4(Apr 26, 2022)
Flux v0.29.4 is patch release with memory consumption improvements for the reconciliation of HelmRepository resources.

Note that v0.29.0 includes breaking changes.

Components Changelog

source-controller to v0.24.2

CLI Changelog

PR #2679 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(29.33 KB)
flux_0.29.4_checksums.txt(1.17 KB)
flux_0.29.4_checksums.txt.pem(1.43 KB)
flux_0.29.4_checksums.txt.sig(96 bytes)
flux_0.29.4_darwin_amd64.tar.gz(14.93 MB)
flux_0.29.4_darwin_arm64.tar.gz(14.85 MB)
flux_0.29.4_linux_amd64.tar.gz(14.21 MB)
flux_0.29.4_linux_arm.tar.gz(13.36 MB)
flux_0.29.4_linux_arm64.tar.gz(12.97 MB)
flux_0.29.4_sbom.spdx.json(368.68 KB)
flux_0.29.4_source_code.tar.gz(390.43 KB)
flux_0.29.4_windows_386.zip(14.15 MB)
flux_0.29.4_windows_amd64.zip(14.41 MB)
flux_0.29.4_windows_arm64.zip(13.16 MB)
install.yaml(349.39 KB)
manifests.tar.gz(30.29 KB)
v0.29.3(Apr 22, 2022)
Flux v0.29.3 is patch release which fixes a regression bug where the source-controller would panic in further to be identified edge-case scenarios in which a HelmRepository Artifact would not have a Size.

In addition, the flags for configuring the exponential back-off retry have been made available in the kustomize-controller.

Note that v0.29.0 includes breaking changes.

Components Changelog

source-controller to v0.24.1

kustomize-controller to v0.24.3

CLI Changelog

PR #2668 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(29.32 KB)
flux_0.29.3_checksums.txt(1.17 KB)
flux_0.29.3_checksums.txt.pem(1.43 KB)
flux_0.29.3_checksums.txt.sig(96 bytes)
flux_0.29.3_darwin_amd64.tar.gz(14.93 MB)
flux_0.29.3_darwin_arm64.tar.gz(14.84 MB)
flux_0.29.3_linux_amd64.tar.gz(14.21 MB)
flux_0.29.3_linux_arm.tar.gz(13.36 MB)
flux_0.29.3_linux_arm64.tar.gz(12.97 MB)
flux_0.29.3_sbom.spdx.json(368.68 KB)
flux_0.29.3_source_code.tar.gz(390.43 KB)
flux_0.29.3_windows_386.zip(14.15 MB)
flux_0.29.3_windows_amd64.zip(14.41 MB)
flux_0.29.3_windows_arm64.zip(13.16 MB)
install.yaml(349.39 KB)
manifests.tar.gz(30.29 KB)
v0.29.2(Apr 21, 2022)
Flux v0.29.2 is patch release that comes with dependency updates to please static security analyzers.

Note that v0.29.0 includes breaking changes.

Components Changelog

kustomize-controller to v0.24.2

notification-controller to v0.23.4

CLI Changelog

PR #2662 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(29.32 KB)
flux_0.29.2_checksums.txt(1.17 KB)
flux_0.29.2_checksums.txt.pem(1.43 KB)
flux_0.29.2_checksums.txt.sig(96 bytes)
flux_0.29.2_darwin_amd64.tar.gz(14.93 MB)
flux_0.29.2_darwin_arm64.tar.gz(14.84 MB)
flux_0.29.2_linux_amd64.tar.gz(14.21 MB)
flux_0.29.2_linux_arm.tar.gz(13.36 MB)
flux_0.29.2_linux_arm64.tar.gz(12.97 MB)
flux_0.29.2_sbom.spdx.json(368.68 KB)
flux_0.29.2_source_code.tar.gz(390.30 KB)
flux_0.29.2_windows_386.zip(14.15 MB)
flux_0.29.2_windows_amd64.zip(14.41 MB)
flux_0.29.2_windows_arm64.zip(13.16 MB)
install.yaml(349.39 KB)
manifests.tar.gz(30.29 KB)
v0.29.1(Apr 20, 2022)
Flux v0.29.1 is patch release that comes with a regression bug fix for Kustomizations files that contain remote references.

Note that v0.29.0 includes breaking changes.

Components Changelog

kustomize-controller to v0.24.1

CLI Changelog

PR #2657 - @hiddeco - Update kustomize-controller to v0.24.1

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(29.33 KB)
flux_0.29.1_checksums.txt(1.17 KB)
flux_0.29.1_checksums.txt.pem(1.43 KB)
flux_0.29.1_checksums.txt.sig(96 bytes)
flux_0.29.1_darwin_amd64.tar.gz(14.93 MB)
flux_0.29.1_darwin_arm64.tar.gz(14.84 MB)
flux_0.29.1_linux_amd64.tar.gz(14.21 MB)
flux_0.29.1_linux_arm.tar.gz(13.36 MB)
flux_0.29.1_linux_arm64.tar.gz(12.97 MB)
flux_0.29.1_sbom.spdx.json(368.68 KB)
flux_0.29.1_source_code.tar.gz(390.45 KB)
flux_0.29.1_windows_386.zip(14.15 MB)
flux_0.29.1_windows_amd64.zip(14.41 MB)
flux_0.29.1_windows_arm64.zip(13.16 MB)
install.yaml(349.39 KB)
manifests.tar.gz(30.29 KB)
v0.29.0(Apr 20, 2022)
Flux v0.29.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes

source-controller

From this release on, the RUNTIME_NAMESPACE environment variable is no longer taken into account to configure the advertised HTTP/S address of the storage. Instead, variable substitution must be used, as described in the changelog entry for v0.5.2.

Use of file-based KubeConfig options are now permanently disabled (e.g. TLSClientConfig.CAFile, TLSClientConfig.KeyFile, TLSClientConfig.CertFile and BearerTokenFile). The drive behind the change was to discourage insecure practices of mounting Kubernetes tokens inside the controller's container file system.

Use of TLSClientConfig.Insecure in KubeConfig file is disabled by default, but can be enabled at controller level with the flag --insecure-kubeconfig-tls.

Use of ExecProvider in KubeConfig file is now disabled by default, but can be enabled at controller level with the flag --insecure-kubeconfig-exec.

Features and improvements

Notification Improvements

A new notification is now emitted to identify recovery from failures. It is triggered when a failed reconciliation is followed by a successful one, and the notification message is the same that's sent in usual successful source reconciliation message about the stored artifact.

In-memory cache for HelmRepository

The opt-in in-memory cache for HelmRepository addresses issues where the index file is loaded and unmarshalled in concurrent reconciliation resulting in a heavy memory footprint. It can be configured using the flags: --helm-cache-max-size, --helm-cache-ttl, --helm-cache-purge-interval.

Configurable retention of Source Artifacts

Garbage Collection is enabled by default, and now its retention options are configurable with the flags: --artifact-retention-ttl (default: 60s) and --artifact-retention-records (default: 2). They define the minimum time to live and the maximum amount of artifacts to survive a collection.

Configurable Key Exchange Algorithms for SSH connections

The Key Exchange Algorithms used when establishing SSH connections are based on the defaults configured upstream in go-git and golang.org/x/crypto. Now this can be overriden with the flag --ssh-kex-algos. Note this applies to the go-git gitImplementation or the libgit2 gitImplementation but only when Managed Transport is being used.

Configurable Exponential Back-off retry settings

The exponential back-off retry can be configured with the new flags: --min-retry-delay (default: 750ms) and --max-retry-delay (default: 15min). Previously the defaults were set to 5ms and 1000s, which in some cases impaired the controller's ability to self-heal (e.g. retrying failing SSH connections).

Experimental managed transport for libgit2 Git implementation

Managed Transport for libgit2 now introduces self-healing capabilities, to recover from failure when long-running connections become stale.

SOPS refactored and optimized

SOPS implementation was refactored to include various improvements and extended code coverage. Age identities are now imported once and reused multiple times, optimizing CPU and memory usage between decryption operations.

Helm chart directory loader improvements

Introduction of a secure directory loader which improves the handling of Helm charts paths.

Components Changelog

helm-controller to v0.20.1

kustomize-controller to v0.24.0

source-controller to v0.24.0

notification-controller to v0.23.3

image-reflector-controller to v0.17.2

image-automation-controller to v0.22.0

Other changes since last minor release:

helm-controller to v0.19.0

kustomize-controller to v0.23.0

source-controller to v0.23.0

CLI Changelog

PR #2652 - @fluxcdbot - Update toolkit components

PR #2649 - @hiddeco - Update dependencies

PR #2646 - @aryan9600 - Handle secret types properly while masking sops data

PR #2631 - @canidam - bootstrap git: Allow the password to be specified with GIT_PASSWORD env var

PR #2624 - @kingdonb - Add detail to delete docs

PR #2617 - @fluxcdbot - Update toolkit components

PR #2616 - @SomtochiAma - Add cli flags for chart interval and reconcile strategy

PR #2611 - @souleb - Add an option to diff with a local Flux Kustomization file

PR #2609 - @darkowlzz - monitoring-config: set grafana dashboards labelValues

PR #2607 - @souleb - [Diff] Update pkg/kustomize to v0.1.0

PR #2597 - @stefanprodan - [RFC-0002] Flux OCI support for Helm

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(29.32 KB)
flux_0.29.0_checksums.txt(1.17 KB)
flux_0.29.0_checksums.txt.pem(1.43 KB)
flux_0.29.0_checksums.txt.sig(96 bytes)
flux_0.29.0_darwin_amd64.tar.gz(14.93 MB)
flux_0.29.0_darwin_arm64.tar.gz(14.84 MB)
flux_0.29.0_linux_amd64.tar.gz(14.21 MB)
flux_0.29.0_linux_arm.tar.gz(13.36 MB)
flux_0.29.0_linux_arm64.tar.gz(12.97 MB)
flux_0.29.0_sbom.spdx.json(368.68 KB)
flux_0.29.0_source_code.tar.gz(390.29 KB)
flux_0.29.0_windows_386.zip(14.15 MB)
flux_0.29.0_windows_amd64.zip(14.41 MB)
flux_0.29.0_windows_arm64.zip(13.16 MB)
install.yaml(349.39 KB)
manifests.tar.gz(30.29 KB)
v0.28.5(Mar 30, 2022)
Flux v0.28.5 is a patch release that comes with various improvements and dependency updates to the controller components. Please consult the changelogs from the list below for a precise overview of changes. Users are (as always) encouraged to upgrade for the best experience.

Note that if you are upgrading from v0.27 you need to follow the Upgrade Flux to the Source v1beta2 API guide.

Components Changelog

kustomize-controller to v0.22.3

source-controller to v0.22.5

image-automation-controller to v0.21.3

notification-controller to v0.23.2

CLI Changelog

PR #2594 - @fluxcdbot - Update toolkit components

PR #2584 - @souleb - Diff: Update homeport/Dyff to v1.5.2

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(30.68 KB)
flux_0.28.5_checksums.txt(1.17 KB)
flux_0.28.5_checksums.txt.pem(1.43 KB)
flux_0.28.5_checksums.txt.sig(96 bytes)
flux_0.28.5_darwin_amd64.tar.gz(14.91 MB)
flux_0.28.5_darwin_arm64.tar.gz(14.82 MB)
flux_0.28.5_linux_amd64.tar.gz(14.19 MB)
flux_0.28.5_linux_arm.tar.gz(13.35 MB)
flux_0.28.5_linux_arm64.tar.gz(12.96 MB)
flux_0.28.5_sbom.spdx.json(366.60 KB)
flux_0.28.5_source_code.tar.gz(382.64 KB)
flux_0.28.5_windows_386.zip(14.14 MB)
flux_0.28.5_windows_amd64.zip(14.39 MB)
flux_0.28.5_windows_arm64.zip(13.14 MB)
install.yaml(348.80 KB)
manifests.tar.gz(30.08 KB)
v0.28.4(Mar 28, 2022)
Flux v0.28.4 is a patch release that comes with improvements to the experimental managed transport's overall stability. Users are encouraged to upgrade for the best experience.

Note that if you are upgrading from v0.27 you need to follow the Upgrade Flux to the Source v1beta2 API guide.

Components Changelog

source-controller to v0.22.4

image-automation-controller to v0.21.2

CLI Changelog

PR #2583 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(30.67 KB)
flux_0.28.4_checksums.txt(1.17 KB)
flux_0.28.4_checksums.txt.pem(1.43 KB)
flux_0.28.4_checksums.txt.sig(96 bytes)
flux_0.28.4_darwin_amd64.tar.gz(14.91 MB)
flux_0.28.4_darwin_arm64.tar.gz(14.82 MB)
flux_0.28.4_linux_amd64.tar.gz(14.19 MB)
flux_0.28.4_linux_arm.tar.gz(13.35 MB)
flux_0.28.4_linux_arm64.tar.gz(12.96 MB)
flux_0.28.4_sbom.spdx.json(366.59 KB)
flux_0.28.4_source_code.tar.gz(383.06 KB)
flux_0.28.4_windows_386.zip(14.13 MB)
flux_0.28.4_windows_amd64.zip(14.39 MB)
flux_0.28.4_windows_arm64.zip(13.14 MB)
install.yaml(348.80 KB)
manifests.tar.gz(30.09 KB)
v0.28.3(Mar 25, 2022)
Flux v0.28.3 is patch release that comes with a regression bug fix for SOPS Azure Key Vault decryption. In addition, Kustomize has been updated to v4.5.3 to address an issue with YAML anchors. Users are encouraged to upgrade for the best experience.

Note that if you are upgrading from v0.27 you need to follow the Upgrade Flux to the Source v1beta2 API guide.

Components Changelog

source-controller to v0.22.3

kustomize-controller to v0.22.2

helm-controller to v0.18.2

CLI Changelog

PR #2577 - @fluxcdbot - Update toolkit components

PR #2572 - @stefanprodan - Add the kube client qps and burst to the global args

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(30.70 KB)
flux_0.28.3_checksums.txt(1.17 KB)
flux_0.28.3_checksums.txt.pem(1.43 KB)
flux_0.28.3_checksums.txt.sig(96 bytes)
flux_0.28.3_darwin_amd64.tar.gz(14.91 MB)
flux_0.28.3_darwin_arm64.tar.gz(14.82 MB)
flux_0.28.3_linux_amd64.tar.gz(14.19 MB)
flux_0.28.3_linux_arm.tar.gz(13.35 MB)
flux_0.28.3_linux_arm64.tar.gz(12.96 MB)
flux_0.28.3_sbom.spdx.json(366.59 KB)
flux_0.28.3_source_code.tar.gz(383.11 KB)
flux_0.28.3_windows_386.zip(14.13 MB)
flux_0.28.3_windows_amd64.zip(14.39 MB)
flux_0.28.3_windows_arm64.zip(13.14 MB)
install.yaml(348.80 KB)
manifests.tar.gz(30.09 KB)
v0.28.2(Mar 24, 2022)
Flux v0.28.2 is patch release that comes with a regression bug fix for notification spam. Users are encouraged to upgrade for the best experience.

Note that if you are upgrading from v0.27 you need to follow the Upgrade Flux to the Source v1beta2 API guide.

Components Changelog

kustomize-controller to v0.22.1

CLI Changelog

PR #2570 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(30.68 KB)
flux_0.28.2_checksums.txt(1.17 KB)
flux_0.28.2_checksums.txt.pem(1.43 KB)
flux_0.28.2_checksums.txt.sig(96 bytes)
flux_0.28.2_darwin_amd64.tar.gz(14.67 MB)
flux_0.28.2_darwin_arm64.tar.gz(14.58 MB)
flux_0.28.2_linux_amd64.tar.gz(13.97 MB)
flux_0.28.2_linux_arm.tar.gz(13.13 MB)
flux_0.28.2_linux_arm64.tar.gz(12.75 MB)
flux_0.28.2_sbom.spdx.json(359.24 KB)
flux_0.28.2_source_code.tar.gz(382.40 KB)
flux_0.28.2_windows_386.zip(13.92 MB)
flux_0.28.2_windows_amd64.zip(14.18 MB)
flux_0.28.2_windows_arm64.zip(12.96 MB)
install.yaml(348.80 KB)
manifests.tar.gz(30.08 KB)
v0.28.1(Mar 23, 2022)
Flux v0.28.1 is patch release that comes with a regression bug fix for image update automation. Users are encouraged to upgrade for the best experience.

Note that if you are upgrading from v0.27 you need to follow the Upgrade Flux to the Source v1beta2 API guide.

Components Changelog

helm-controller to v0.18.1

source-controller to v0.22.2

notification-controller to v0.23.1

image-reflector-controller to v0.17.1

image-automation-controller to v0.21.1

CLI Changelog

PR #2569 - @fluxcdbot - Update toolkit components

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(30.67 KB)
flux_0.28.1_checksums.txt(1.17 KB)
flux_0.28.1_checksums.txt.pem(1.43 KB)
flux_0.28.1_checksums.txt.sig(96 bytes)
flux_0.28.1_darwin_amd64.tar.gz(14.67 MB)
flux_0.28.1_darwin_arm64.tar.gz(14.58 MB)
flux_0.28.1_linux_amd64.tar.gz(13.97 MB)
flux_0.28.1_linux_arm.tar.gz(13.13 MB)
flux_0.28.1_linux_arm64.tar.gz(12.75 MB)
flux_0.28.1_sbom.spdx.json(359.24 KB)
flux_0.28.1_source_code.tar.gz(382.40 KB)
flux_0.28.1_windows_386.zip(13.92 MB)
flux_0.28.1_windows_amd64.zip(14.18 MB)
flux_0.28.1_windows_arm64.zip(12.96 MB)
install.yaml(348.80 KB)
manifests.tar.gz(30.08 KB)
v0.28.0(Mar 23, 2022)
Flux v0.28.0 comes with new reconcilers for Source kinds and graduates the Flux Source API to v1beta2.

Breaking changes

From this version on, controllers depending on Source kinds (kustomize-controller, helm-controller and image-automation-controller) do now require the Source v1beta2 Custom Resource Definition to be present on the cluster.

Features and improvements

API specifications in a user-friendly format

The new specifications for the v1beta2 API have been written in a new format with the aim to be more valuable to a user. Featuring separate sections with examples, and information on how to write and work with them.

Artifact now advertises size

The size (in bytes) of a tarball Artifact is now advertised in the Size (.size) field of the Artifact. This can be utilized by users to e.g. quickly see if .sourceignore rules have an effect, or be displayed in a UI.

Azure Blob Storage support for Bucket resources

The .spec.provider of a Bucket resource can now be set to azure to instruct the source-controller to use the Azure Blob Storage SDK while fetching objects. This allows for authenticating using Service Principals, Managed Identities and Shared Keys.

For more information, see the Bucket spec about the Azure provider.

Azure Key Vault multi-tenancy

Kustomization resources making use of SOPS with Azure Key Vault as the backing KMS are now allowed to refer to Azure credentials in the tenant's namespace.

For more information, see the Kustomization spec about Azure Key Vault Secret entries.

Enhanced Kubernetes Conditions

Source API resources will now advertise more explicit Condition types (more about the types in API changes), provide Reconciling and Stalled Conditions where applicable for better integration with kstatus, and record the Observed Generation on the Condition.

For a detailed overview per Source type, refer to the spec:

GitRepository

HelmRepository

HelmChart

Bucket

Enhanced Kubernetes Events (and notifications)

The Kubernetes Events the source-controller emits have been reworked to provide a proper reason, and more informative messages. Users making use of the notification-controller will notice this as well, as this same information is used to compose notifications.

Experimental managed transport for libgit2 Git implementation

The libgit2 Git implementation supports a new experimental transport to improve reliability, adding timeout enforcement for Git network operations. Opt-in by setting the environment variable EXPERIMENTAL_GIT_TRANSPORT to true in the source-controller and/or image-automation-controller their Deployment.

This will result in the low-level transport being handled by the controller, instead of libgit2. It may result in an increased number of timeout messages in the logs, however it will remove the ability of Git operations to make the controllers hang indefinitely.

Manage cluster addons

A new annotation (kustomize.toolkit.fluxcd.io/ssa: merge) is available for allowing Flux to patch cluster addons such as CoreDNS without the kustomize-controller removing the kubectl managed fields.

For more information, see the Kustomization spec about reconciliation.

Reuse of HTTP/S transport for Helm repository index and chart downloads

The Helm dependency has been updated to v3.8.1, with a patch applied from https://github.com/helm/helm/pull/10568. Using this patch, the HTTP transports are now managed by the source-controller, to prevent the clogging of thousands of open TCP connections on some instances.

Update of libgit2 Git implementation to v1.3.x

The libgit2 Git implementation has been updated to v1.3.x, allowing us to provide better error signals for authentication, certificate and transport failures. Effectively, this means that instead of a unable to clone: User error string, a descriptive one is now given.

In addition, NO_PROXY settings are now properly taken into account.

Preparation of support for rsa-ssh2-256/512

The dependency on golang.org/x/crypto has been updated to v0.0.0-20220315160706-3147a52a75dd, as preparation of support for rsa-ssh2-256/512. This should theoretically work out of the box for known_hosts entries and go-git Git provider credentials, but has not been widely tested.

API changes

The source.toolkit.fluxcd.io/v1beta2 API is backwards compatible with v1beta1.

Introduction of Reconciling and Stalled Condition types for better integration with kstatus.

Introduction of new Condition types to provide better signals and failure indications:

ArtifactOutdated: indicates the current Artifact of the Source is outdated.

SourceVerified: indicates the integrity of the Source has been verified.

FetchFailed: indicates a transient or persistent fetch failure of the upstream Source.

BuildFailed: indicates a transient or persistent build failure of a Source's Artifact.

StorageOperationFailed: indicates a transient or persistent failure related to storage.

IncludeUnavailable: indicates an include is not available. For example, because it does not exist, or does not have an Artifact.

Introduction of a Size (in bytes) field (.status.artifact.size) in the Artifact object.

Introduction of ObservedChartName (.status.observedChartName) and ObservedSourceArtifactRevision (.status.observedSourceArtifactRevision) fields in the HelmChart Status.

Introduction of azure provider implementation for Bucket.

Upgrade procedure

To upgrade your cluster, download the Flux CLI binary from the release page and rerun the flux bootstrap command. This will upgrade the Flux components on your cluster to the latest version. Other upgrade options can be found on the docs website.

ℹ️ Note that updating the manifests in Git from source.toolkit.fluxcd.io/v1beta1 to source.toolkit.fluxcd.io/v1beta2 can be done at any time after the Flux components upgrade. All users are encouraged to update the manifests as any deprecated fields will be removed when the next API version will be released. For more information, see post upgrade.

Terrafrom upgrade

When using the Terraform provider for Flux, you have to manually remove the v1beta2 GitRepository from the TF state:

terraform state rm 'kubectl_manifest.sync["source.toolkit.fluxcd.io/v1beta1/gitrepository/flux-system/flux-system"]'

Other upgrade methods

When upgrading without the CLI or Terraform (using e.g. GitHub Actions or RenovateBot), we recommend to bump the GitRepository API version in gotk-sync.yaml to v1beta2.

Post upgrade

After rolling out the upgrade, and when you have confirmed things to be working as expected. Resources in Git which refer to source.toolkit.fluxcd.io/v1beta1 can be updated to refer to source.toolkit.fluxcd.io/v1beta2:

@@ -1,4 +1,4 @@ -apiVersion: source.toolkit.fluxcd.io/v1beta1 +apiVersion: source.toolkit.fluxcd.io/v1beta2 kind: GitRepository metadata: name: gitrepository-sample

Components Changelog

helm-controller to v0.18.0

kustomize-controller to v0.22.0

source-controller to v0.22.1

notification-controller to v0.23.0

image-reflector-controller to v0.17.0

image-automation-controller to v0.21.0

CLI Changelog

PR #2566 - @stefanprodan - Fix resume source bucket panic

PR #2565 - @hiddeco - fix: wait for Source objects observed generation

PR #2564 - @stefanprodan - Use absolute domain name for the events address

PR #2561 - @hiddeco - Update toolkit components

PR #2559 - @stefanprodan - Retry bootstrap operations on Git conflict errors

PR #2542 - @fluxcdbot - Update toolkit components

PR #2530 - @stefanprodan - Add components-extra example usage to CLI help

PR #2512 - @souleb - Introduce a printer interface for flux resources

PR #2484 - @cuishuang - all: fix some typos

PR #2483 - @fluxcdbot - Update toolkit components

PR #2467 - @darkowlzz - Update get subcommand column order

Source code(tar.gz)
Source code(zip)
crd-schemas.tar.gz(30.68 KB)
flux_0.28.0_checksums.txt(1.17 KB)
flux_0.28.0_checksums.txt.pem(1.43 KB)
flux_0.28.0_checksums.txt.sig(96 bytes)
flux_0.28.0_darwin_amd64.tar.gz(14.67 MB)
flux_0.28.0_darwin_arm64.tar.gz(14.58 MB)
flux_0.28.0_linux_amd64.tar.gz(13.97 MB)
flux_0.28.0_linux_arm.tar.gz(13.13 MB)
flux_0.28.0_linux_arm64.tar.gz(12.75 MB)
flux_0.28.0_sbom.spdx.json(359.24 KB)
flux_0.28.0_source_code.tar.gz(382.40 KB)
flux_0.28.0_windows_386.zip(13.92 MB)
flux_0.28.0_windows_amd64.zip(14.18 MB)
flux_0.28.0_windows_arm64.zip(12.96 MB)
install.yaml(348.80 KB)
manifests.tar.gz(30.08 KB)