Re: prune images from registry - getsockopt: connection timed out

On Wed, Oct 11, 2017 at 10:44 AM, Maciej Zarczynski < m.zarczyn...@adbglobal.com> wrote: > Hi, > > for a while we are running openshift origin standalone docker-registry > and it works pretty well, but when i try to prune images i am facing > following situation: > > [root@c37ee07bf04f /]# time

prune images from registry - getsockopt: connection timed out

Hi, for a while we are running openshift origin standalone docker-registry and it works pretty well, but when i try to prune images i am facing following situation: [root@c37ee07bf04f /]# time oc adm prune images --keep-tag-revisions=10 --confirm error: error communicating with registry

Re: Origin router and X-Forwarded-For

Sorry I meant it say, it *cannot modify the http request in any way. On Thu, 12 Oct 2017 at 12:51 am, Joel Pearson wrote: > Hi Marcelo, > > If you use Passthrough termination then that means that OpenShift cannot > add the X-Forwarded-For header, because as the

Re: Origin router and X-Forwarded-For

Hi Marcelo, If you use Passthrough termination then that means that OpenShift cannot add the X-Forwarded-For header, because as the name suggests it is just passing the packets through and because it’s encrypted it can modify the http request in anyway. If you want X-Forwarded-For you will need

Origin router and X-Forwarded-For

Hi All, we tried to configure a route on Origin 3.6 with a Passthrough termination to an Apache webserver present into a single POD but we can't notice the X-Forwarded-Header to Apache logs. We tried to capture it without success. Could you confirm if there are some method to extract it from the