flux2: flux bootstrap failing | context deadline exceeded

Describe the bug

Whenever I try bootstrap in flux github it always ends with client rate limiter Wait returned an error: context deadline exceeded

Steps to reproduce

  1. Install flux
  2. Bootstrap github controller

Expected behavior

Flux would bootstrap github controller properly and with no issues, same as the steps provided in fluxcd.io

Screenshots and recordings

:~$ flux bootstrap github --owner=$GITHUB_USER --repository=fleet-infra --branch=main --path=./clusters/my-cluster --personal --timeout 10m ► connecting to github.com ► cloning branch “main” from Git repository “https://github.com/IamEarlJohn/fleet-infra.git” ✔ cloned repository ► generating component manifests '# Warning: ‘patchesJson6902’ is deprecated. Please use ‘patches’ instead. Run ‘kustomize edit fix’ to update your Kustomization automatically. ✔ generated component manifests ✔ committed sync manifests to “main” (“b871f2aa54076cf6c129f383cecc8c8c182bc527”) ► pushing component manifests to “https://github.com/IamEarlJohn/fleet-infra.git” ► 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 ✗ client rate limiter Wait returned an error: context deadline exceeded ► confirming components are healthy ✔ helm-controller: deployment ready ✔ kustomize-controller: deployment ready ✔ notification-controller: deployment ready ✔ source-controller: deployment ready ✔ all components are healthy ✗ bootstrap failed with 1 health check failure(s)


:~$ kubectl -n flux-system get pods NAME READY STATUS RESTARTS AGE helm-controller-c8466f78b-rthtf 1/1 Running 1 (3h31m ago) 6d22h kustomize-controller-666f8f4b5f-588n2 1/1 Running 1 (3h31m ago) 6d22h notification-controller-55d78c78c-9wqcn 1/1 Running 1 (3h31m ago) 6d22h source-controller-557989894-mphsv 1/1 Running 1 (3h31m ago) 6d22h

OS / Distro

Ubuntu 20.04

Flux version

flux version 2.0.0-rc.5

Flux check

:~$ flux check ► checking prerequisites ✔ Kubernetes 1.26.3 >=1.20.6-0 ► checking controllers ✔ helm-controller: deployment ready ► ghcr.io/fluxcd/helm-controller:v0.34.1 ✔ kustomize-controller: deployment ready ► ghcr.io/fluxcd/kustomize-controller:v1.0.0-rc.4 ✔ notification-controller: deployment ready ► ghcr.io/fluxcd/notification-controller:v1.0.0-rc.4 ✔ source-controller: deployment ready ► ghcr.io/fluxcd/source-controller:v1.0.0-rc.5 ► checking crds ✔ alerts.notification.toolkit.fluxcd.io/v1beta2 ✔ buckets.source.toolkit.fluxcd.io/v1beta2 ✔ gitrepositories.source.toolkit.fluxcd.io/v1 ✔ helmcharts.source.toolkit.fluxcd.io/v1beta2 ✔ helmreleases.helm.toolkit.fluxcd.io/v2beta1 ✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2 ✔ kustomizations.kustomize.toolkit.fluxcd.io/v1 ✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2 ✔ providers.notification.toolkit.fluxcd.io/v1beta2 ✔ receivers.notification.toolkit.fluxcd.io/v1 ✔ all checks passed

Git provider

Github (Personal account)

Container Registry provider

No response

Additional context

:~$ flux logs 2023-06-14T01:31:52.220Z info Kustomization/flux-system.flux-system - Source is not ready, artifact not found 2023-06-14T01:41:52.219Z info Kustomization/flux-system.flux-system - Source is not ready, artifact not found 2023-06-14T01:51:52.213Z info Kustomization/flux-system.flux-system - Source is not ready, artifact not found 2023-06-14T02:01:52.212Z info Kustomization/flux-system.flux-system - Source is not ready, artifact not found 2023-06-14T02:11:52.213Z info Kustomization/flux-system.flux-system - Source is not ready, artifact not found 2023-06-14T02:21:52.213Z info Kustomization/flux-system.flux-system - Source is not ready, artifact not found 2023-06-14T02:31:52.207Z info Kustomization/flux-system.flux-system - Source is not ready, artifact not found

Code of Conduct

  • I agree to follow this project’s Code of Conduct

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Comments: 19 (6 by maintainers)

Most upvoted comments

► determining if source secret “flux-system/flux-system” exists ✔ source secret up to date

It seems you had the source secret on the cluster already. Can you try deleting it and running the same bootstrap command again so that it recreates it?

kubectl delete -n flux-system secret flux-system
flux bootstrap ....

I did try to delete the flux-system secret and re-run the flux bootstrap command, now it works as the screenshot below:

image