Flux-system kustomization issue in kubernetes

Ayan Ghoshal 0 Reputation points
2024-08-07T07:31:48.5433333+00:00

Hello i am using the fluxCD Extension in azure kubernetes services, from the past few hours the reconciliation is not happening and i am getting the below error. What might be the issue?

{"level":"error","ts":"2024-08-07T07:18:54.884Z","msg":"Reconciliation failed after 739.692645ms, next try in 2m0s","controller":"kustomization","controllerGr

oup":"kustomize.toolkit.fluxcd.io","controllerKind":"Kustomization","Kustomization":{"name":"flux-system-kustomization","namespace":"flux-system"},"namespace"

:"flux-system","name":"flux-system-kustomization","reconcileID":"1f549271-2da5-41b4-afda-0a51fd71949e","revision":"main@sha1:515acbbe76592caec9b2adb251f32e32c

c42b427","error":"CustomResourceDefinition/helmcharts.source.toolkit.fluxcd.io dry-run failed (Invalid): CustomResourceDefinition.apiextensions.k8s.io "helmc

harts.source.toolkit.fluxcd.io" is invalid: status.storedVersions[1]: Invalid value: "v1": must appear in spec.versions"}

Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,456 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Abiola Akinbade 29,490 Reputation points Volunteer Moderator
    2024-08-07T07:51:40.35+00:00

    Hello Ayan Ghoshal,

    Thanks for your question.

    from the error message problem is with the status.storedVersions[1] field, which contains "v1" but this version is not present in spec.versions.

    Conside upgrading:

    flux get all -A #to get the exact reconciliation issue
    flux upgrade
    	
    

    You can mark it 'Accept Answer' and 'Upvote' if this helped you

    Regards,

    Abiola


  2. Anonymous
    2024-08-08T10:12:20.6433333+00:00

    Hi Ayan Ghoshal,

    Since the Microsoft Q&A community has a policy that the question author cannot accept their own answer. They can only accept answers by others, Summarized and posted the solution that you shared, request you to Accept the answer, it will benefit the community find the answers quickly.

    Scenario:

    Flux-system kustomization issue in Kubernetes.

    Issue:

     I am using the fluxCD Extension in azure kubernetes services, from the past few hours the reconciliation is not happening and i am getting the below error. What might be the issue?

    {"level":"error","ts":"2024-08-07T07:18:54.884Z","msg":"Reconciliation failed after 739.692645ms, next try in 2m0s","controller":"kustomization","controllerGr

    oup":"kustomize.toolkit.fluxcd.io","controllerKind":"Kustomization","Kustomization":{"name":"flux-system-kustomization","namespace":"flux-system"},"namespace"

    Things Tried:

    Resolved this issue by changing the spec versions of multiple Custom Resource Definitions (CRDs) in gotk yaml file.

    Shared by @Ayan Ghoshal

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.