I have a Kubernetes cluster on AWS. I have nginx,flux and gitlab installed in it.Gitlab and nginx are in one namespace and flux is in another namespace…Gitlab is running as a node port and is behind Nginx ( so it is accessible via a url like - https://aa82ee1b284b0464bb1353bd2fbccdd2-1957445678.ca-central-1.elb.amazonaws.com/gitlab from the outside- externally)
In the flux logs i see this:
ts=2020-09-22T11:48:16.396057979Z caller=images.go:17 component=sync-loop msg="polling for new images for automated workloads"
ts=2020-09-22T11:48:16.396109955Z caller=images.go:27 component=sync-loop msg="no automated workloads"
ts=2020-09-22T11:48:42.995779454Z caller=loop.go:101 component=sync-loop err="git repo not ready: git clone --mirror: fatal: Could not read from remote repository., full output:\n Cloning into bare repository '/tmp/flux-gitclone802701812'...\nssh: Could not resolve hostname aa82ee1b284b0464bb1353bd2fbccdd2-1957445678.ca-central-1.elb.amazonaws.com:root: Name does not resolve\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n"
I have uploaded my public key to SSH keys section of Gitlab. And i have my private key.
When i run this - git clone git@aa82ee1b284b0464bb1353bd2fbccdd2-1957445678.ca-central-1.elb.amazonaws.com:root/automation.git, nothing happens.
nginx LoadBalancer 100.69.214.156 aa82ee1b284b0464bb1353bd2fbccdd2-1957445678.ca-central-1.elb.amazonaws.com 443:31944/TCP,5269:32174/TCP,22:32333/TCP
gitlab NodePort 100.68.131.43 8084:31587/TCP,8085:31067/TCP,222:31231/TCP,8223:32121/TCP
I am able to clone with https from the flux pod without any problems, but not with ssh.
What could be the reason for this error ?