-
Notifications
You must be signed in to change notification settings - Fork 68
GIT authentication is not working during cluster setup #44
Comments
It seems that this problem is already fixed in the master branch: Is it possible to update the Google Cloud version with this fix? @barney-s the last marketplace build is from July 2018: Can we have an update to this image? |
Will work on updating the cloud marketplace. |
Hi @barney-s However I was forced to use the mysql spec configurations because both the Postgres and CloudSQL specs are not working. If I use the CloudSQL spec I get this error when the database connection is starting: If I use the Postgres spec I get a similar error: Should I create a new issue for this? |
Thanks @jcunhasilva |
Feel free to reopen if you for tracking cloud marketplace availability. |
I created the following cluster using the airflow operator deployed directly from Google Cloud Marketplace:
Once the cluster is up and running, I get the following error in the git-sync side container:
Cloning into '/git'...\nfatal: could not read Username for 'https://github.com': No such device or address\n"
So it seems the container is struggling with GIT authentication. When inspecting the container's environment variables I can see that these variables were created:
I stumbled upon this issue in the git-sync project where other people had issues setting up authentication:
kubernetes/git-sync#126
In this issue we have the following configuration
so it seems the airflow-operator is using the wrong prefix for the authentication ("GIT_" instead of "GIT_SYNC_")
The text was updated successfully, but these errors were encountered: