[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: HTTP and HTTPS routes



In 1.1 we added a field to a single route that allows it to be exposed insecure if you have tls config.  On your HTTPS route, set "insecureEdgeTerminationPolicy" to "Allow" (I think).

On Jan 7, 2016, at 3:09 PM, Diego Castro <diego castro getupcloud com> wrote:

Hello, i've create an application and two routes for the same hostname, one for http and other for https.

I can confirm the haproxy config get's updated and both routes seems to be up and green but i can't reach them via browser, looks like is either one or other not both.

Can you confirm if is the expected behavior?

Here's my routes:

apiVersion: v1
items:
- apiVersion: v1
  kind: Route
  metadata:
    creationTimestamp: 2016-01-07T19:36:50Z
    labels:
      app: site
    name: http
    namespace: huotr
    resourceVersion: "1457689"
    selfLink: /oapi/v1/namespaces/huotr/routes/http
    uid: ff91b392-b575-11e5-9e06-000d3ac01d22
  spec:
    port:
      targetPort: "8080"
    to:
      kind: Service
      name: site
  status: {}
- apiVersion: v1
  kind: Route
  metadata:
    annotations:
    creationTimestamp: 2016-01-07T19:27:14Z
    labels:
      app: site
    name: site
    namespace: huotr
    resourceVersion: "1457284"
    selfLink: /oapi/v1/namespaces/huotr/routes/site
    uid: a7c893ad-b574-11e5-99aa-000d3ac0312b
  spec:
    port:
      targetPort: "8080"
    tls:
      termination: edge
    to:
      kind: Service
      name: site
  status: {}
kind: List
metadata: {}

_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]