OpenShift Routes Explained¶

Introduction¶

OpenShift Routes publish a Service through the cluster router. Route troubleshooting should confirm the route host, service target, endpoints, TLS termination mode, and router events.

Core Concepts¶

OpenShift builds on Kubernetes with projects, Routes, ImageStreams, Builds, Operators, SCCs, and integrated platform administration.

Practical Examples¶

oc get route web -n app

oc describe route web -n app

oc get service web -n app

oc get endpoints web -n app

curl -Ik https://web-app.apps.ocp.example.com

Example output:

NAME   HOST/PORT                         PATH   SERVICES   PORT   TERMINATION   WILDCARD
web    web-app.apps.ocp.example.com              web        8080   edge          None

Example YAML¶

apiVersion: route.openshift.io/v1
kind: Route
metadata:
  name: web
spec:
  host: web-app.apps.ocp.example.com
  to:
    kind: Service
    name: web
  port:
    targetPort: 8080
  tls:
    termination: edge

Verification¶

oc get route web -n app

oc get endpoints web -n app

curl -Ik https://web-app.apps.ocp.example.com

Common Mistakes¶

• Debugging the route before checking service endpoints.
• Using edge TLS when the backend expects passthrough TLS.
• Forgetting that route hostnames must be unique unless wildcard policy is configured.

Quick Checklist¶

• Confirm the active project.
• Inspect the exact object named in the error.
• Read recent events.
• Apply one focused fix.
• Verify status after the change.

Related Guides¶

• Openshift Vs Kubernetes
• Openshift Cli oc Explained
• Openshift Projects Vs Namespaces

Summary¶

OpenShift Routes Explained is best understood through the OpenShift objects involved and the oc commands that verify their current state.