Closed donofriov closed 3 years ago
Suspicion that this has to do with the cache (enabled here), which has seen a bug fix upstream awhile ago https://github.com/kubernetes-sigs/cli-utils/pull/279.
Can you please try the binary in the attachment? This has UseCache
set to false
.
I'm able to successfully bootstrap with the patched version:
❯ ~/Downloads/bin/flux-darwin-patched check
► checking prerequisites
✔ kubectl 1.20.2 >=1.18.0-0
✔ Kubernetes 1.18.9-eks-d1db3c >=1.16.0-0
► checking controllers
✔ helm-controller: healthy
► ghcr.io/fluxcd/helm-controller:v0.7.0
✔ kustomize-controller: healthy
► ghcr.io/fluxcd/kustomize-controller:v0.8.1
✔ notification-controller: healthy
► ghcr.io/fluxcd/notification-controller:v0.8.0
✔ source-controller: healthy
► ghcr.io/fluxcd/source-controller:v0.8.1
✔ all checks passed
❯ flux bootstrap...
◎ verifying installation
✔ install completed
► configuring deploy key
✔ deploy key configured
► generating sync manifests
✔ sync manifests pushed
► applying sync manifests
◎ waiting for cluster sync
✔ bootstrap finished
❯ kubectl get secrets
NAME TYPE DATA AGE
default-token-dfzgb kubernetes.io/service-account-token 3 61m
flux-system Opaque 3 2m49s
helm-controller-token-6ntwx kubernetes.io/service-account-token 3 61m
kustomize-controller-token-7hzpr kubernetes.io/service-account-token 3 61m
notification-controller-token-g5pxh kubernetes.io/service-account-token 3 61m
source-controller-token-9wpcr kubernetes.io/service-account-token 3 61m
Can you, for the sake of confirming the PR above is indeed the right fix, try it once again with the binary from the attached tarball? If that comes back :green_circle: we are good to go.
Thank you! :sunflower:
Looks good 🎉
Describe the bug
After completing all of the pre-requisites and then running the
flux bootstrap
command, I'm getting✗ install failed
even though the kubernetes resources (deploys, pods, secrets, etc.) are up and running without any errors.I'm trying to migrate from flux v1 to flux v2. This means that flux v1 is already installed on the cluster in the flux namespace. I've created a new repository for flux v2 and have attempted to bootstrap it with no workloads as not to sync v1 and v2 together. All the v2 repo has is the
gotk-components.yaml
file from theAdd flux v0.8.2 components manifests
commit.To Reproduce
Steps to reproduce the behaviour:
Expected behavior
I'd expect the bootstrap to complete without any errors
Additional context
Running the
flux check
command printed out three different results running the command three different times right after each other:Here is the describe from the
helm-controller
deploy that never returns a status check:Below please provide the output of the following commands: