Skip to content

Commit b0e45af

Browse files
committed
Updated README openshift support for hybrid
1 parent a9ff4d9 commit b0e45af

1 file changed

Lines changed: 25 additions & 1 deletion

File tree

kubernetes/helm-hybrid/README.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ kubectl get pods -n tyk-dp -w
164164

165165
### 6. Access Services
166166

167-
There are three ways to access your Tyk Gateway, ordered from quickest to most production-ready:
167+
There are four ways to access your Tyk Gateway, ordered from quickest to most production-ready:
168168

169169
#### Option 1: LoadBalancer Service (Quickest for Cloud Deployments)
170170

@@ -395,6 +395,30 @@ ingress:
395395

396396
---
397397

398+
#### Option 4: OpenShift Routes (RedHat OpenShift)
399+
400+
OpenShift uses Routes rather than Ingress or LoadBalancer for external access. Routes are created using the `oc` CLI and are automatically assigned a hostname under your cluster's `*.apps` domain.
401+
402+
> **For local testing on OpenShift Local (CRC), port-forwarding (Option 2) is recommended** as it avoids DNS configuration.
403+
404+
**Expose the Gateway via a Route:**
405+
406+
```bash
407+
# Expose Gateway
408+
oc expose svc gateway-svc-tyk-dp-tyk-gateway -n tyk-dp --port=8080
409+
410+
# Get the assigned Route URL
411+
oc get routes -n tyk-dp
412+
```
413+
414+
The Gateway Route will be available at a URL such as:
415+
416+
```text
417+
http://gateway-svc-tyk-dp-tyk-gateway-tyk-dp.apps.<cluster-domain>
418+
```
419+
420+
---
421+
398422
### 7. Verify Data Plane Connection
399423

400424
```bash

0 commit comments

Comments
 (0)