I installed Waypoint on an EKS cluster running behind a corporate proxy. I am trying to connect to VSC from the UI, but Github Organization is rejecting HTTPS connections, so I need to connect via SSH. However, the Corporate Proxy blocks port 22.
I’m starting to understand a little more now, but a new mystery has arisen. A profile with PROXY settings is placed for the ODR generated from the Static runner:
I set up a Private Key for the GitHub App and entered the following in the Source URL: ssh://org-<orgid>@ssh.github.com:443/orgame/reponame.git
From stdout of the odr, I could see that it is trying to access the site via HTTPS, but when I check the Proxy server log, nothing is recorded. The server could not be reached. Does ODR not respect PROXY environment variables?
@k21205 - One thing I would check is when an on-demand runner is spawned, those environment variables you’ve set for your runner profile is actually set on the runner. You might need to update your Kubernetes cluster to not clean up short-lived tasks (which is what ODR spawns as in k8s), but if you can get access to the ODR pod, are those environment variables set?
This ensures that environment variables are properly assigned. Environment variables are properly assigned. I noticed that SSH over HTTPS is only an SSH protocol even if the port is 443. Therefore, these Proxy settings are ignored…
So I tried to access the repository on an HTTPS basis using the Github App installation ID: https://x-access-token:ghs_<token>@github.com/<orgname>/<reponame>.git
It is interesting to note that while accessing this URL locally successfully retrieves refs, Waypoint ODR returns the following log from go-git: