Re: OpenShift registry behind registry auth issues

After some internal discussion we've decided that we'll fix this by adding the service ip address to the default NO_PROXY list. Follow the bug for any further updates. On Tue, Nov 21, 2017 at 10:29 AM, Scott Dodson wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1511870

Re: OpenShift registry behind registry auth issues

https://bugzilla.redhat.com/show_bug.cgi?id=1511870 is the bug, we haven't fixed it yet. We're debating whether or not to switch to using the dns name, though if environment variables evaluate as expected perhaps we should just add NO_PROXY=${KUBENETES_SERVICE_HOST} and then we can address whether

Re: OpenShift registry behind registry auth issues

On Tue, Nov 21, 2017 at 1:46 AM, Joel Pearson wrote: > Hi, > > I spend most of the day debugging why my OpenShift registry wasn’t working > because the cluster lives behind a http proxy. I can see OpenShift ansible > configured the registry with proxy settings

OpenShift registry behind registry auth issues

Hi, I spend most of the day debugging why my OpenShift registry wasn’t working because the cluster lives behind a http proxy. I can see OpenShift ansible configured the registry with proxy settings including no_proxy, but in the error logs I could see during authentication it was trying to talk