OKD 3.11 Router with HAProxy 2.1 and TLS 1.3

Hi. There was a question in the openshift-dev channel from @Josef how to build the OKD 3.11 Router with newer HAProxy version. I have now created a new OKD Router image with HAProxy 2.1 and TLS 1.3 and pushed it to docker hub. https://hub.docker.com/repository/docker/me2digital/okd-router

Re: Router

knew there is a namespace label on every project and all the routes created in that project by default use that namespace router You can create as many routes as you want for the same service. With router sharding can you define on which router which route should be exposed https

Router

routes created in that project by default use that namespace router -- Srinivas Kotaru ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev

Re: [3.x]: openshift router and its own metrics

reference/ suggestion where i should open > it for OKD ? i guess BZ is not the suitable for OKD, or am i wrong ? > There should be BZ components for origin > Thoughts? > > > Cheers, > Dani > > > On Thu, Aug 15, 2019 at 3:59 PM Clayton Coleman > wrote: > >

Re: [3.x]: openshift router and its own metrics

n > it for OKD ? i guess BZ is not the suitable for OKD, or am i wrong ? > > > Thoughts? > > > Cheers, > Dani > > > On Thu, Aug 15, 2019 at 3:59 PM Clayton Coleman > wrote: > >> Metrics memory use in the router should be proportional to number of >> services, e

Re: [3.x]: openshift router and its own metrics

File a bug with more details, can’t say off the top of my head Thoughts? Cheers, Dani On Thu, Aug 15, 2019 at 3:59 PM Clayton Coleman wrote: > Metrics memory use in the router should be proportional to number of > services, endpoints, and routes. I doubt it's leaking there and

Re: [3.x]: openshift router and its own metrics

PM Clayton Coleman wrote: > Metrics memory use in the router should be proportional to number of > services, endpoints, and routes. I doubt it's leaking there and if it were > it'd be really slow since we don't restart the router monitor process > ever. Stats should d

Re: [3.x]: openshift router and its own metrics

On Thu, Aug 15, 2019 at 3:30 PM Dan Mace wrote: > > > On Thu, Aug 15, 2019 at 10:03 AM Daniel Comnea > wrote: > >> Hi, >> >> Would appreciate if anyone can please confirm that my understanding is >> correct w.r.t the way the router haproxy image [1] is

Re: [3.x]: openshift router and its own metrics

Metrics memory use in the router should be proportional to number of services, endpoints, and routes. I doubt it's leaking there and if it were it'd be really slow since we don't restart the router monitor process ever. Stats should definitely be preserved across reloads,

Re: [3.x]: openshift router and its own metrics

On Thu, Aug 15, 2019 at 10:03 AM Daniel Comnea wrote: > Hi, > > Would appreciate if anyone can please confirm that my understanding is > correct w.r.t the way the router haproxy image [1] is built. > Am i right to assume that the image [1] is is built as it's seen without >

[3.x]: openshift router and its own metrics

Hi, Would appreciate if anyone can please confirm that my understanding is correct w.r.t the way the router haproxy image [1] is built. Am i right to assume that the image [1] is is built as it's seen without any other layer being added to include [2] ? Also am i right to say the haproxy me

Router PR

Hi, Would it be possible for anyone with enough power to merge the following PR? https://github.com/openshift/router/pull/5 as I have been waiting for it for quite a while now. Cheers, Iago. ___ dev mailing list dev@lists.openshift.redhat.com http

Re: [kubevirt-dev] How to add get your route detected by router?

eo description. Have a nice day El 2019-01-29 12:38, Shyam Biradar escribió: > Hi Petr, > > Thanks for the quick reply. Yes, I was talking about routes. I have figured > out few things. > Like how router automatically admits routes and what we need to to for > external con

Re: [kubevirt-dev] How to add get your route detected by router?

Hi Petr, Thanks for the quick reply. Yes, I was talking about routes. I have figured out few things. Like how router automatically admits routes and what we need to to for external connectivity to services. Thanks. For now I am all set. [image: logo] *Shyam Biradar* * Software Engineer | DevOps

How to add get your route detected by router?

Hi, My router is not detecting service routes automatically. This is the first time I am trying router on openshift. Is it expected that router should admin services automatically? Can we manually make a route get resolved by router? [image: logo] *Shyam Biradar* * Software Engineer | DevOps

Default HAProxy router dashboard not working

Hi, I deployed default HAProxy router following the doc <https://docs.openshift.com/container-platform/3.11/install_config/router/default_haproxy_router.html> Using default ports. 80, 443. Then added a route to the router service. Made hostname resolvable from my desktop and then tried acc

Re: who to build origin-haproxy-router binary only ?

Hi Oliver, I am not the expert here but I have built origin. If you are making changes to the actual router code then you need to build the binary and then build the images. It looks like you are building on Mac based on your output so you will have to build in containers. Make sure you have

who to build origin-haproxy-router binary only ?

Hi I want to tweak the *origin-haproxy-router*. But I don't know how to just build the router binary. Can you give me some advice? This doesn't work. # 1 This doesn't work. .*/build-local-images.py openshift/origin-haproxy-router* [INFO] Building haproxy-router... Traceback (m

Openshift router with h2 and print_headers

Hi all. I have created a openshift router image with the new haproxy 1.8 . https://hub.docker.com/r/me2digital/openshift-ocp-router-hap18/ The haproxy 1.8 have added a lot of feature and one of them is h2 (=http/2). I have added also a smal lua script which prints the incomming http headers

Re: Question about router usage

? Could router be used? For example, I want to deploy redis cluster in openshift cluster. Redis cluster is using TCP protocol and listening on port 6379. Could I expose redis service port 6379 with router? If not, how could I expose the service to external clients? Could I use nodePort provided by

Question about router usage

Hi guys, How could I expose services using TCP/UDP protocols to external clients? Could router be used? For example, I want to deploy redis cluster in openshift cluster. Redis cluster is using TCP protocol and listening on port 6379. Could I expose redis service port 6379 with router? If not

Re: Router Defaut Timeout

;> On Aug 9, 2016, at 4:02 PM, Ram Ranganathan wrote: >> >> That default for the haproxy router can be set via an environment >> variable in your deployment. >> >> $ oc env dc/$router_dc_name ROUTER_SLOWLORIS_TIMEOUT=30s >> >> If you want to set it on

Re: Router Defaut Timeout

Coleman wrote: > Is this a new variable in 1.3? Can we rename it to be more descriptive? > ROUTER_HTTP_REQUEST_TIMEOUT would be more accurate. > > On Aug 9, 2016, at 4:02 PM, Ram Ranganathan wrote: > > That default for the haproxy router can be set via an environment variable &g

Re: Router Defaut Timeout

Is this a new variable in 1.3? Can we rename it to be more descriptive? ROUTER_HTTP_REQUEST_TIMEOUT would be more accurate. On Aug 9, 2016, at 4:02 PM, Ram Ranganathan wrote: That default for the haproxy router can be set via an environment variable in your deployment. $ oc env dc

Re: Router Defaut Timeout

That default for the haproxy router can be set via an environment variable in your deployment. $ oc env dc/$router_dc_name ROUTER_SLOWLORIS_TIMEOUT=30s If you want to set it on a per route basis, add an annotation to the route. See: https://github.com/openshift/origin/blob/master/images/router

Router Defaut Timeout

Is there any way to change the default timeout settings at router image? Found this: https://github.com/openshift/origin/blob/master/images/router/haproxy/conf/haproxy-config.template#L42 ___ dev mailing list dev@lists.openshift.redhat.com http

Re: Router Pod stuck at pending

tcp6 0 0 :::41670:::*LISTEN On Thu, Apr 7, 2016 at 6:48 PM, Rajat Chopra wrote: > It sounds like a port conflict. Something occupying port 1936 on master? > That port is used by the router for stats. > > /Rajat > > On Thu, Apr 7,

Re: Router Pod stuck at pending

It sounds like a port conflict. Something occupying port 1936 on master? That port is used by the router for stats. /Rajat On Thu, Apr 7, 2016 at 10:39 AM, Mfawa Alfred Onen wrote: > I have enabled scheduling on the master node and still have it stuck at > pending and the same error.

Re: Router Pod stuck at pending

I have enabled scheduling on the master node and still have it stuck at pending and the same error. Also I cross checked the labels on the master and it has region=infra. ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.co

Re: Router Pod stuck at pending

On 04/06/2016 06:03 PM, Mfawa Alfred Onen wrote: > 1. oc get nodes > > NAME STATUS AGE > master.dev.local Ready,SchedulingDisabled 8d ... > Note: Based on the selector (--selector="region=infra"), it is scheduling it > on the master node. but the master

Router Pod stuck at pending

.dev.localReady 8d *2. oc get pods* NAME READY STATUS RESTARTS AGE docker-registry-1-deploy 0/1 DeadlineExceeded 0 22m docker-registry-2-pbvcf1/1 Running0 21m router-1-deploy

Router command is updated to be more flexible

As a cluster administrator, you should no longer have to provide any arguments to creating a router. Simply invoke `oc adm router` or `oadm router` as a cluster administrator and a new router should be created with the proper permissions (you'll be prompted to grant access if you don'

Router image v1.1.3 updated due to a backwards incompatible change.

Thanks to @wenskys for reporting https://github.com/openshift/origin/issues/7452 - in v1.1.3 the router began writing status for routes (when the route was accepted, or an error message if a duplicate route exists) which required the system:router role to have permission to update routes. However

Re: Router: Readiness probe failed - connection refused

specified in haproxy-config.template file. On Wed, Feb 17, 2016 at 6:03 PM, Clayton Coleman wrote: > Seems like a bug in either the router image or the router settings. > > On Feb 17, 2016, at 4:26 PM, Rishi Misra > wrote: > > Hmm .. odd, this is what I get in event monitor: &g

Re: Router: Readiness probe failed - connection refused

Seems like a bug in either the router image or the router settings. On Feb 17, 2016, at 4:26 PM, Rishi Misra wrote: Hmm .. odd, this is what I get in event monitor: 2:55:08 PM Pod router-1-zw83z Unhealthy Readiness probe failed: 401 Unauthorized You need a valid user and password to access

Re: Router: Readiness probe failed - connection refused

Hmm .. odd, this is what I get in event monitor: 2:55:08 PM Pod router-1-zw83z Unhealthy Readiness probe failed: 401 Unauthorized You need a valid user and password to access this content. (3 times in the last 20 seconds) On Wed, Feb 17, 2016 at 3:58 PM, Clayton Coleman wrote: > The readin

Re: Router: Readiness probe failed - connection refused

obe entries from router dc. However, I'd like to know why http > probes are not working. It seems like username/password are not being > passed in the request. Router config does have these entries defined: > > - name: STATS_PASSWORD > value: xx

Re: Router: Readiness probe failed - connection refused

Thanks Ram - I was able to get around it using by removing Liveness and Readiness probe entries from router dc. However, I'd like to know why http probes are not working. It seems like username/password are not being passed in the request. Router config does have these entries de

Re: Deploying router manually

is what you'd need. HTH On Tue, Feb 9, 2016 at 11:28 AM, Paul Weil wrote: > You may use node selectors to force the router to a particular node. This > is done with the --selector option of the oadm router command. > > For more information on scheduler configuration pl

Re: Deploying router manually

You may use node selectors to force the router to a particular node. This is done with the --selector option of the oadm router command. For more information on scheduler configuration please see: https://docs.openshift.org/latest/admin_guide/scheduler.html On Tue, Feb 9, 2016 at 2:14 PM

Deploying router manually

I looked at https://github.com/openshift/origin/blob/master/docs/routing.md - section on deploying router manually - and it noted "To run the router manually (outside of a pod) you should first build the images with instructions found below". I had already build my router images but d

Re: Router Sharding

s across all the various trello boards map >to releases. > >> >> >> -- >> Srinivas Kotaru >> >> >> >> >> >> >> On 1/15/16, 12:30 PM, "Brenton Leanhardt" wrote: >> >>>On Fri, Jan 15, 2016 at 12:47 PM, Srinivas Naga

Re: Router Sharding

o see how cards across all the various trello boards map > to releases. > >> >> >> -- >> Srinivas Kotaru >> >> >> >> >> >> >> On 1/15/16, 12:30 PM, "Brenton Leanhardt" wrote: >> >>>On Fri, Jan 15, 2016 at 1

Re: Router Sharding

PM, Srinivas Naga Kotaru (skotaru) >> wrote: >>> >>> Brenton said you guys are working on router sharding >>> >>> https://trello.com/c/DtPlixdb/49-8-router-sharding-traffic-ingress >>> >>> I didn’t get quite well description. What is t

Re: Router Sharding

Thanks Brenton. It is clear now. When this feature will be released? 3.2? -- Srinivas Kotaru On 1/15/16, 12:30 PM, "Brenton Leanhardt" wrote: >On Fri, Jan 15, 2016 at 12:47 PM, Srinivas Naga Kotaru (skotaru) > wrote: >> >> Brenton said you guys are working on

Re: Router Sharding

On Fri, Jan 15, 2016 at 12:47 PM, Srinivas Naga Kotaru (skotaru) wrote: > > Brenton said you guys are working on router sharding > > https://trello.com/c/DtPlixdb/49-8-router-sharding-traffic-ingress > > I didn’t get quite well description. What is this feature, how it is usef

Router Sharding

Brenton said you guys are working on router sharding https://trello.com/c/DtPlixdb/49-8-router-sharding-traffic-ingress I didn’t get quite well description. What is this feature, how it is useful, what are the use cases and when it will be released? Can we create separate routers for internal