Re: Passthrough TLS route not working

Hm, then you lose the ability to do cookie based load balancing On Fri, Jan 19, 2018, 5:11 PM Joel Pearson wrote: > In the reference implementation they use Classic ELB load balancers in TCP > mode: > > See this cloud formation template: >

Re: Passthrough TLS route not working

In the reference implementation they use Classic ELB load balancers in TCP mode: See this cloud formation template: https://github.com/openshift/openshift-ansible-contrib/blob/master/reference-architecture/aws-ansible/playbooks/roles/cloudformation-infra/files/greenfield.json.j2#L763 On Sat, Jan

Re: Passthrough TLS route not working

What mode are you running the AWS load balancers in? You probably want to run them as TCP load balancers and not HTTP. That way as you say the SNI will not get messed with. On Sat, 20 Jan 2018 at 4:45 am, Marc Boorshtein wrote: > So if I bypass the AWS load balancer,

Re: Passthrough TLS route not working

So if I bypass the AWS load balancer, everything works great. Why doesn't HAProxy like the incoming requests? I'm trying to debug the issue by enabling logging with oc set env dc/router ROUTER_SYSLOG_ADDRESS=127.0.0.1 ROUTER_LOG_LEVEL=debug But the logging doesn't seem to get there (I also

Passthrough TLS route not working

I'm running origin 3.7 on AWS. I have an AWS load balancer in front of my infrastructure node. I have a pod listening on TLS on port 9090. The service links to the pod and then I have a route that is setup with passthrough tls to the pod, but every time i try to access it I get the "Application

Re: Help using ImageStreams, DCs and ImagePullSecrets templates with a GitLab private registry (v3.6)

Louis, In our case, it is Artifactory. Relevant headers: HTTP/1.1 401 Unauthorized Server: Artifactory/5.4.5 X-Artifactory-Id: X-Artifactory-Node-Id: WWW-Authenticate: Basic realm="Artifactory Realm" Note however that in the case of Artifactory, Docker registries have to be fronted by