Github bootstrap keeps failing, am I missing something? #3887
Answered
by
stefanprodan
jonmahoney15
asked this question in
Q&A
-
|
Hi I followed the guide to bootstrap flux into my cluster, add it to my existing repo, and to pull my apps images. It paases all prechecks: ~ ❯ flux check --pre base ⎈ kubernetes-admin@kubernetes 23:08:18
► checking prerequisites
✔ Kubernetes 1.24.1 >=1.20.6-0
✔ prerequisites checks passedI then export the github PAT token I created and my github username. Then I run the following to bootstrap: flux bootstrap github --components-extra=image-reflector-controller,image-automation-controller --owner=jonmahoney15 --repository=PersonalSite --branch=main --path=Infrastructure --read-write-key --personal --private=falseBut I receive this output where its stalls on the kustomization step: I did: flux logs --level=erroroutput: So its able to pull the repo, make a commit, add the manifests then for some reason it errors out. I am not sure if I am making a mistake somewhere. Any help would be greatly appreciated |
Beta Was this translation helpful? Give feedback.
Answered by
stefanprodan
May 16, 2023
Replies: 2 comments
-
This means that your cluster DNS is broken, you need to look into your network settings |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
kingdonb
-
|
This issue is near the top google search for this issue, so any future googlers - this is how I solved this issue (it's because of the cluster domain names run kubectl get cm/coredns -o yaml -n kube-systemYou'll get the configMap wit your domain name, like this apiVersion: v1
data:
Corefile: |-
---- lines removed for brevity ---
kubernetes stag.mehar.internal in-addr.arpa ip6.arpa { <=== see this line
pods insecure
fallthrough in-addr.arpa ip6.arpa
}Then run the bootstrap command, add the --cluster-domain field flux bootstrap github \
--cluster-domain stag.mehar.internal \ <=== see this line
--owner=$GITHUB_USER \
--repository=fleet-infra \
--branch=main \
--path=./clusters/my-cluster \
--personal |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This means that your cluster DNS is broken, you need to look into your network settings