Ingress controller do not create the route if TLS is used

Solution Unverified - Updated -

Issue

  • one or more pods are exposed to the public via the ingress controller
  • the ingress object is defined with a TLS edge termination similar to the following:

     apiVersion: extensions/v1beta1
      kind: Ingress
      metadata:
        name: web-tls-test
      spec:
        rules:
        - host: foo.bar.com
          http:
            paths:
            - backend:
                serviceName: web-svc
                servicePort: 80
              path: /
        tls:
        - hosts:
          - foo.bar.com
    
  • after creating the Ingress object the Route is not created

Environment

  • Red Hat OpenShift Container Platform (OCP)
    • 3.x
    • 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content