flux_bootstrap_git
do not deploy resources in cluster
#564
Labels
request for feedback
Feedback is requested from users
Hey Flux team 馃憢
I tried to migrate Flux tf provider to 1.1.2 following the migration guide, and I updated the flux version to
2.0.0-rc5
but I have a weird issue: the manifests get pushed to the repo as expected, however I don't see any pods in theflux-system
namespace anymore.The terraform apply do not fail, and I've tried to rerun the bootstrap several times by updating the flux version (so that a change gets detected and the bootstrap rerun). So everytime the manifests get pushed to the repo, but no reconciliation is done because there's no pod to perform it.
At some point I thought maybe the use of
provider.flux.kubernetes.token
was the issue, so I tried as well withprovider.flux.kubernetes.exec
but it's the same result.I'm currently blocked at "dev" upgrade, but I can't really move to my other clusters if I don't understand this :(
I tried to look into the issues here, didn't find something similar. Any chance anyone could help with this please ?
The
iam_role
assumed to run the apply is part of"system:masters"
and didn't change during migration.Below the resource in the terraform state (remove most of the content for
kustomization_override
,repository_files.gotk-components.yaml
andrepository_files.gotk-sync.yaml
for brevity):Thanks.
The text was updated successfully, but these errors were encountered: