Hi.
On 23.01.20 21:44, Srinivas Naga Kotaru (skotaru) wrote:
Quick question
Is it possible to expose different routers for different routes on same
project? One approach is create different projects but we have a use case where
we want to expose different routers for different routers. We kne
Thank you all, i'll give it a try.
2016-08-09 17:14 GMT-03:00 Ram Ranganathan :
> Yeah, its new in 1.3 - was done as part of the changes for
> https://bugzilla.redhat.com/show_bug.cgi?id=1328037
> The name I think came from the bug description but that said yeah,
> ROUTER_HTTP_REQUEST_TIMEOUT wou
Yeah, its new in 1.3 - was done as part of the changes for
https://bugzilla.redhat.com/show_bug.cgi?id=1328037
The name I think came from the bug description but that said yeah,
ROUTER_HTTP_REQUEST_TIMEOUT
would be more
descriptive/accurate. CCing Jacob.
On Tue, Aug 9, 2016 at 1:07 PM, Clayton Col
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/$router_dc_n
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/h
Hello Rajat, I don't think anything is occupying port 1936. Here is the
output of *netstat -lnt*
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp0 0 0.0.0.0:51630 0.0.0.0:* LISTEN
tcp
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. Also I cro
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
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
Thanks ... must be something wrong with my image. I rebuilt my rhel-based
images using HAProxy 1.6 with following changes to
conf/haproxy-config.template file:
listen stats
bind :{{.StatsPort}}
{{ else }}
listen stats
bind :1936
It seems like HAProxy 1.6 does not like the format specifie
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 this
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 readiness
The readiness and liveness probes don't support authentication - the health
check, even if stats are enabled, should not require authorization.
On Wed, Feb 17, 2016 at 3:16 PM, Rishi Misra
wrote:
> Thanks Ram - I was able to get around it using by removing Liveness and
> Readiness probe entries
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 defined:
Thanks Brenton sharing overview page to see what are upcoming features or
changes. Very handy ..
--
Srinivas Kotaru
On 1/15/16, 1:49 PM, "Brenton Leanhardt" wrote:
>On Fri, Jan 15, 2016 at 3:53 PM, Srinivas Naga Kotaru (skotaru)
> wrote:
>> Thanks Brenton. It is clear now. When this fea
All of the core work for this is in 3.1.1, except for the ability to
report back which routers the route is being served by to the API and
UI.
On Fri, Jan 15, 2016 at 4:49 PM, Brenton Leanhardt wrote:
> On Fri, Jan 15, 2016 at 3:53 PM, Srinivas Naga Kotaru (skotaru)
> wrote:
>> Thanks Brenton. I
On Fri, Jan 15, 2016 at 3:53 PM, Srinivas Naga Kotaru (skotaru)
wrote:
> Thanks Brenton. It is clear now. When this feature will be released? 3.2?
That card has the 'committed-3.3' label in trello so that's really the
best guidance I can give.
In general https://ci.openshift.redhat.com/releases_
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 router sharding
>>
>> https:
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 useful,
> what are the us
19 matches
Mail list logo
