images are not fetched using HelmRelease

[kadzielawa]

Hello,
thank you for your powerful tool, I really like it! great job ! it's big milestone to gitops :)
I have problem with fluxcd2 because during creating processes which would be automatically after pushing images to ECR repository, HelmRelease is not upgrading containers however ImageUpdateAutomation works great and helm values file is updated on git repository very well.

not upgrading containers - I mean that even in repository the image is in the newest version eg.(sdd9) container is still in wrong version...
do you have any ideas what it's wrong with those files?

flux logs doesn't return nothing special... I see only that every one minute updating working.

something like values.yaml are not valid recognize by kubernetes

Every 2.0s: flux get images all                                                                                                                                                                                                                                                                                            iMac-Jakub.local: Sun Apr 11 09:45:36 2021

NAME                    READY   MESSAGE                         LAST SCAN                       SUSPENDED
imagerepository/podinfo True    successful scan, found 34 tags  2021-04-11T09:44:46+02:00       False

NAME                    READY   MESSAGE                                                                                                 LATEST IMAGE
imagepolicy/podinfo     True    Latest image tag for '247635813899.dkr.ecr.eu-central-1.amazonaws.com/hey-flux' resolved to: sdd9      247635813899.dkr.ecr.eu-central-1.amazonaws.com/hey-flux:sdd9

NAME                                    READY   MESSAGE                                                         LAST RUN                        SUSPENDED
imageupdateautomation/flux-system       True    no updates made; last commit 58dd783 at 2021-04-11T07:35:46Z    2021-04-11T09:44:53+02:00       False

structure (my-private-repo)
-file1.yml
-file2.yml
-file3.yml
---eks(directory)
-------heyflux(directory)
----------values.yaml
----------Chart.yaml
----------rest chart files

file1.yml

apiVersion: image.toolkit.fluxcd.io/v1alpha1
kind: ImageUpdateAutomation
metadata:
  name: flux-system
  namespace: flux-system
spec:
  checkout:
    branch: master
    gitRepositoryRef:
      name: podinfo
  commit:
    authorEmail: [email protected]
    authorName: fluxcdbot
    messageTemplate: '{{range .Updated.Images}}{{println .}}{{end}}'
  interval: 1m0s
  push:
    branch: master
  update:
    path: ./eks/heyflux
    strategy: Setters

file2.yml

---
apiVersion: image.toolkit.fluxcd.io/v1alpha1
kind: ImageRepository
metadata:
  name: podinfo
  namespace: flux-system
spec:
  image: 247635813899.dkr.ecr.eu-central-1.amazonaws.com/hey-flux
  interval: 1m0s
  secretRef:
    name: aws-ecr
---
apiVersion: image.toolkit.fluxcd.io/v1alpha1
kind: ImagePolicy
metadata:
  name: podinfo
  namespace: flux-system
spec:
  imageRepositoryRef:
    name: podinfo
  filterTags:
    pattern: '^sdd[a-fA-F0-9]+'
  policy:
    alphabetical:
      order: asc

file3.yml:

apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: GitRepository
metadata:
  name: podinfo
  namespace: flux-system
spec:
  interval: 1m
  url: ssh://[email protected]/muumerepos/my-private-repo.git
  secretRef:
    name: ssh-credentials
  ref:
    branch: master
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: heyflux
  namespace: flux-system
spec:
  interval: 1m
  upgrade:
    remediation:
      retries: -1
  chart:
    spec:
      chart: ./eks/heyflux
      valuesFile: ./eks/heyflux/values.yaml
      sourceRef:
        kind: GitRepository
        name: podinfo
        namespace: flux-system
      interval: 1m

eks/heyflux/values.yaml

# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1
envName: "default"
strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 25%
muumeerp:
  image:
    repository: 247635813899.dkr.ecr.eu-central-1.amazonaws.com/hey-flux
    tag: sdd9 # {"$imagepolicy": "flux-system:podinfo:tag"}
    pullPolicy: Always
  service:
    type: ClusterIP
    port: 8080

[Legion2]

The values.yaml in the chart directory is automatically used by the chart, you don't have to explicitly set valuesFile to point to it. I also try to use a helm chart from my git repository with image automation and have the same problem, see #1244. The problem is that we have to update the version in the Chart.yaml to trigger a update rollout.

[Legion2]

@kadzielawa As the image update was already committed to you repo, the problem is not really related to image update automation. However, it must have something to do with the source-controller or helm-controller. You should inspect the events and status of the HelmRelease and HelmChart objects.

[kadzielawa]

Hello again, thank you again for your fast reply.
now, I understand. I missed the basics files - I haven't created Kustomization file inside chart ! I thought that it's not needed. thanks for the explanation.

regards to "automatic images update": Am I understand correctly that even if I will fix it, the cluster won't be updated with the newest image because version of Chart won't change right ? because I will change only image tag by ImageUpdateAutomation and I need to wait for the PR about which @hiddeco said, correct?

[Legion2]

I haven't created Kustomization file inside chart

I don't understand, you have a kustomization in your helm chart?

Am I understand correctly that even if I will fix it, the cluster won't be updated with the newest image because version of Chart won't change right?

yes

[kadzielawa]

based on your suggestions, I took a look into the logs and I had seen:

7m2s        Normal   error    kustomization/flux-system           kustomize create failed: failed to decode Kubernetes YAML from /tmp/flux-system066542639/eks/heyflux/Chart.yaml: error unmarshaling JSON: while decoding JSON: Object 'Kind' is missing in '{"apiVersion":"v2","appVersion":"sdd999","description":"A Helm chart for Kubernetes","name":"heyflux","type":"application","version":"0.2.0"}'

as you can see - probably it looking for the kustomization "Kind" but my Chart.yaml doesn't have it. it's really simple Chart.yaml like that:

apiVersion: v1
name: heyflux
description: A Helm chart for Kubernetes
type: application
version: 0.2.0
appVersion: 1.16.0

but following this tutorial (I have found it after your reply) it requires Kind: Kustomize, I am guessing?
https://github.com/fluxcd/flux2-kustomize-helm-example

[Legion2]

When you installed flux2 using bootstrap command and then there should be a gotk-sync.yaml which already contains a Kustomization, for the clusters/... directory, so all manifests placed into this directory or sub directories are automatically synced. No need for an additional Kustomization.

You error log looks like you your helm chart is in that auto sync directory, which is not good. Instead only the HelmRelease , which references the chart should be part of the sync directory, the helm chart itself should be placed outside in the git repository.