Kubernetes Ingress vs OpenShift Route: Key Differences and How to Use Them

Kubernetes Ingress Overview

Kubernetes Ingress is a native Kubernetes resource that defines how external traffic is routed to services inside a cluster. It acts as an entry point, supporting host and path based routing, load balancing, and optional TLS termination.

OpenShift Route Overview

OpenShift Route is a proprietary OpenShift resource that provides similar external access capabilities. It integrates security features such as OAuth and role‑based access, offers built‑in load balancing, domain routing, and TLS support.

How They Work

Kubernetes Ingress Workflow

Create an Ingress resource that describes routing rules.

Deploy one or more Ingress Controllers that interpret the resource.

The controller parses host and path matches, then forwards traffic to the appropriate backend Pods.

Load balancing and optional SSL/TLS termination are handled by the controller.

Advanced controllers may provide extra routing policies, authentication, and authorization.

OpenShift Route Workflow

Create a Route object that defines host, path, and optional TLS settings.

The OpenShift Router component processes the Route configuration.

The router performs load balancing and forwards requests to the target Service (Pod).

Security integrations such as OAuth and role‑based access can be enabled.

Advanced traffic management features like weight‑based routing are supported.

How to Use Kubernetes Ingress

Step 1: Create a Pod

kind: Pod
metadata:
  name: httpd-pod
  labels:
    app: httpd
spec:
  containers:
  - name: httpd-container
    image: httpd:latest
    ports:
    - containerPort: 80

Step 2: Create a Service

apiVersion: v1
kind: Service
metadata:
  name: httpd-service
spec:
  selector:
    app: httpd
  ports:
  - protocol: TCP
    port: 80
    targetPort: 80

Step 3: Install an Ingress Controller (e.g., ingress‑nginx)

helm upgrade --install ingress-nginx ingress-nginx \
  --repo https://kubernetes.github.io/ingress-nginx \
  --namespace ingress-nginx --create-namespace

Step 4: Define an Ingress Resource

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: httpd-ingress
spec:
  rules:
  - host: httpd.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: httpd-service
            port:
              number: 80

After applying the manifest, accessing httpd.example.com will display the HTTPD welcome page.

How to Use OpenShift Route

CLI Method

apiVersion: route.openshift.io/v1
kind: Route
metadata:
  name: httpd-route
spec:
  to:
    kind: Service
    name: httpd-service
    weight: 100
  port:
    targetPort: 80
  tls:
    termination: edge
    wildcardPolicy: None

Apply with oc create -f httpd-route.yaml and then access the route URL provided by the OpenShift console.

Web Console Method

In the OpenShift console, use the “Create Route” wizard to fill in host, service, and TLS details, then save to generate the route.

Conclusion

Both Kubernetes Ingress and OpenShift Route serve the same fundamental purpose: exposing internal services to external traffic with load balancing, host/path matching, and TLS support. Key differences include:

Ecosystem: Ingress is native to any Kubernetes cluster; Route is specific to OpenShift.

Configuration syntax: Ingress uses standard Kubernetes YAML, while Route uses OpenShift‑specific CRD definitions.

Security features: OpenShift Route offers built‑in OAuth and role‑based access controls that are not part of the generic Ingress spec.

Choosing the appropriate resource depends on the platform you are running and the additional security or integration features you require.