Pods stuck on Init:CrashLoopBackOff #655
Unanswered
ShenghaoHuang
asked this question in
Questions & Answers
Replies: 2 comments
-
Hey I had to overrider the resources and waitformigrations for it to work:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
It will just be something causing it to not be able to connect to github repo. Is the private key in the secret? Is the public key installed at github? Is the secret the same name as specified in values file? Is the secret named id_rsa in the secret? Is the secret in the same namespace? Did you specify "id_rsa" for dags.gitSync.sshSecretKey? (I think that is likely the default anyone). Can you try from the command line with git clone and see if that works? |
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
-
Hello,
Hoping someone can shed some light on this issue I've been running into. I am running Airflow on Kubernetes installed via Helm using KuberentesExecutor. Everything was running fine until I started to try and get gitSync up and running. I saw this problem was posted couple of times before without any solutions so hopefully someone has some insight on why the pods are stuck in Init:CrashLoopBackOff.
Here is my helm values.yaml
values.txt
Here are the description of my pods
I've tried running logs but this is what I get
I saw this issue was posted recently #638
With other people in the comments also running into the same issue without any solution :(
Beta Was this translation helpful? Give feedback.
All reactions