Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to add cert-manager helm repository #112

Open
romanrozinov opened this issue Jun 30, 2024 · 2 comments
Open

Unable to add cert-manager helm repository #112

romanrozinov opened this issue Jun 30, 2024 · 2 comments

Comments

@romanrozinov
Copy link

I am attempting to add infrastructure.yaml structure along with ./infrastructure/** in my own git repository and run against local kind cluster.

I get the following error messages (flux get all):

NAME                            REVISION                SUSPENDED       READY   MESSAGE
gitrepository/flux-system       main@sha1:3a77f8cb      False           True    stored artifact for revision 'main@sha1:3a77f8cb'

NAME                            REVISION                SUSPENDED       READY   MESSAGE
kustomization/flux-system       main@sha1:3a77f8cb      False           True    Applied revision: main@sha1:3a77f8cb
kustomization/infra-configs                             False           False   dependency 'flux-system/infra-controllers' is not ready
kustomization/infra-controllers                         False           False   HelmRepository/cert-manager/cert-manager dry-run failed: no matches for kind "HelmRepository" in version "source.toolkit.fluxcd.io/v1"

Per my understanding, the dependsOn should be forcing the "infra-controllers" kustomization to fire and then install both helmrepository and helmrelease artifact so unsure why I am getting this error message.

I've modeled the ./clusters/kind/infrastructure.yaml and folders ./infrastructure/** identically like this example.

@stefanprodan
Copy link
Member

no matches for kind "HelmRepository" in version "source.toolkit.fluxcd.io/v1"

This tells you that the Flux APIs are missing, you are probably not on Flux v2.3 which promotes HelmRepository to v1

@romanrozinov
Copy link
Author

it does look like I am running flux-v2.2.3 and will have to upgrade to v2.3.0+

C:\Users\rrozi\proj\github\local-k8s-infra-mgmt\infrastructure\controllers [main]> flux --version
flux version 2.3.0
C:\Users\rrozi\proj\github\local-k8s-infra-mgmt\infrastructure\controllers [main]> flux check
► checking prerequisites
✔ Kubernetes 1.30.0 >=1.28.0-0
► checking version in cluster
✔ distribution: flux-v2.2.3
✔ bootstrapped: true
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.37.4
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v1.2.2
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v1.2.4
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v1.2.4
► checking crds
✔ alerts.notification.toolkit.fluxcd.io/v1beta3
✔ buckets.source.toolkit.fluxcd.io/v1beta2
✔ gitrepositories.source.toolkit.fluxcd.io/v1
✔ helmcharts.source.toolkit.fluxcd.io/v1beta2
✔ helmreleases.helm.toolkit.fluxcd.io/v2beta2
✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2
✔ kustomizations.kustomize.toolkit.fluxcd.io/v1
✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2
✔ providers.notification.toolkit.fluxcd.io/v1beta3
✔ receivers.notification.toolkit.fluxcd.io/v1
✔ all checks passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants