You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploying a private endpoint with the "--set proxyUrl=" deploys the pod OK but it doesn't seem to be working as the pod fails to run with a proxy related error.
Looking at the YAML I can see there's a difference in the way the arg is passed for the private endpoint connector vs the kubernetes connector?
Is there any documentation that explains the inner workings of how the proxy arg is translated into the POD and how it uses this proxy to do DNS lookups especially?
The text was updated successfully, but these errors were encountered:
The Pod deployment was successful after adding a few environment variables , like HTTP_PROXY, HTTPS_PROXY and NO_PROXY in the deployment.yaml file . The proxyURL did not work and the container restart. I could see that the endpoint was up and running , However , when I try to configure from the tenable portal , I get an error Unreachable GitHub Enterprise Server Endpoint. I tried to do that nslookup with the address , of my enterpeise server , and it works fine and was able to resolve the ip address , Is there any other tool or command I could use inside the container to debug the connectivity ? Or any other document available to enable debugging mode for tenable?
Deploying a private endpoint with the "--set proxyUrl=" deploys the pod OK but it doesn't seem to be working as the pod fails to run with a proxy related error.
Looking at the YAML I can see there's a difference in the way the arg is passed for the private endpoint connector vs the kubernetes connector?
Is there any documentation that explains the inner workings of how the proxy arg is translated into the POD and how it uses this proxy to do DNS lookups especially?
The text was updated successfully, but these errors were encountered: