Absolutely! You can absolutely pull off URI-unmodified API versioning on OpenShift—no tweaks to URLs required. Here are two practical, production-grade approaches tailored to your needs:

1. Use OpenShift Route's Request Header Matching #

OpenShift's native Route resource supports routing traffic based on HTTP request headers, which lets you direct requests to different API version services without changing the URI at all. You can use custom headers like X-API-Version or standard headers like Accept (for content-type-based versioning) to trigger the routing.

Example Route Configuration #

This route sends default traffic to your v1 API service, but redirects requests with X-API-Version: v2 to the v2 service:

apiVersion: route.openshift.io/v1
kind: Route
metadata:
  name: api-gateway-route
spec:
  host: api.example.com
  # Default backend: v1 API service
  to:
    kind: Service
    name: api-v1-service
    weight: 100
  # Alternate backend for v2 requests
  alternateBackends:
  - kind: Service
    name: api-v2-service
    weight: 0
  # Match rule for v2 requests
  match:
    headers:
      X-API-Version:
        exact: v2

If you prefer RESTful content negotiation, you can match against the Accept header instead:

match:
  headers:
    Accept:
      exact: application/vnd.yourcompany.v2+json

2. Leverage OpenShift Service Mesh (Istio) for Advanced Traffic Control #

For more complex scenarios (like gradual rollouts, A/B testing, or fine-grained request matching), OpenShift Service Mesh (built on Istio) is an excellent choice. It lets you define routing rules based on headers, request parameters, or even payload content—all while keeping the URI identical.

Example VirtualService Configuration #

This VirtualService routes traffic to v1 or v2 based on the X-API-Version header, with a fallback to v1 for unversioned requests:

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: api-virtual-service
spec:
  hosts:
  - api.example.com
  http:
  # Route v1 requests to v1 service
  - match:
    - headers:
        X-API-Version:
          exact: v1
    route:
    - destination:
        host: api-v1-service
        port:
          number: 8080
  # Route v2 requests to v2 service
  - match:
    - headers:
        X-API-Version:
          exact: v2
    route:
    - destination:
        host: api-v2-service
        port:
          number: 8080
  # Default route for unversioned requests
  - route:
    - destination:
        host: api-v1-service
        port:
          number: 8080

Key Notes #

• For Route-based versioning: Ensure your OpenShift cluster is running a version that supports the match field (OpenShift 4.6+ includes this feature).
• For Service Mesh: You'll need to deploy the OpenShift Service Mesh control plane first, and inject sidecars into your API service pods.
• Document the required headers clearly for your API consumers—this ensures everyone knows how to target specific versions without URL changes.

内容的提问来源于stack exchange，提问作者pratik t