S/MF
StackMF Knowledge Base • z/OS
Modernisation & Cloud 11 min read 2026-09-27

Deploying Zowe Server Components on Red Hat OpenShift and Kubernetes for Hybrid Cloud

A
Reviewed by Anshu
Chief Technology Architect & Mainframe Systems SME
Enterprise Modernization Advisory
Google AI Overview & Featured Snippet Quick Answer

Executive Summary: Deploying Zowe Server Components on Red Hat OpenShift and Kubernetes for Hybrid Cloud

Offload compute and simplify Zowe administration by running Zowe server components (APIML, Discovery, Desktop, Caching) inside containerized Red Hat OpenShift or Kubernetes clusters while maintaining secure cross-memory connections to z/OS.

1 Problem Statement & Architecture Context: Deploying Zowe Server Components on Red Hat OpenShift and Kubernetes for Hybrid Cloud

Running all Zowe server address spaces directly on z/OS consumes valuable general-purpose engine capacity and memory, leading to concerns from system programmers regarding z/OS LPAR footprint.

2 Technical Root Cause & Architecture Mechanics

While low-level services (Cross-Memory Server) must execute on z/OS, higher-level services (Zowe API Mediation Layer, Gateway, Web Desktop, Discovery Server) are Java and Node.js microservices.

Zowe for Kubernetes/OpenShift:

  • Packages these services into OCI-compliant container images.
  • Deploys them onto commodity cloud/on-premise Kubernetes clusters.
  • Offloads 80%+ of Zowe's compute overhead away from billable mainframe MSU/MIPS!

3 Implementation Guide & Modernization Strategy

# 1. Deploy via Helm Chart

Configure values.yaml for your Kubernetes cluster:

yaml
zowe:
  domain: zowe.cloud.stackmf.internal
  endpoint:
    host: zsys1.stackmf.internal
    port: 7554
  components:
    gateway:
      replicas: 2
    discovery:
      replicas: 2
    cachingService:
      storage: 5Gi

Deploy the Helm release:

bash
helm install zowe-core oci://zowe-docker-release.jfrog.io/helm/zowe -f values.yaml --namespace zowe --create-namespace

# 2. Verify Pod Health on OpenShift

bash
oc get pods -n zowe

Output:

text
NAME                                READY   STATUS    RESTARTS   AGE
zowe-api-gateway-6d849b4c-2x9la     1/1     Running   0          5m
zowe-discovery-service-7f99b-4k2ml  1/1     Running   0          5m
zowe-caching-service-592b8-9p11z    1/1     Running   0          5m

# 3. Connect to z/OS Subsystems

The containerized gateway establishes outbound mTLS connections to z/OSMF and CICS on z/OS, delivering blazing-fast API routing without consuming mainframe CPU!

Technical Specifications Matrix

Attribute Specification
Target Environment IBM z/OS • Modernisation & Cloud
Key Technologies Zowe, Kubernetes, OpenShift
Delivery SLA Accelerated Sprint Delivery via StackMF Pods
Technical Reviewer Anshu, Chief Technology Architect • StackMF Architecture Pod

Production Readiness & Verification Checklist

? Frequently Asked Questions

What is the root cause of Deploying Zowe Server Components on Red Hat OpenShift and Kubernetes for Hybrid Cloud? ↓
While low-level services (Cross-Memory Server) must execute on z/OS, higher-level services (Zowe API Mediation Layer, Gateway, Web Desktop, Discovery Server) are Java and Node.js microservices.
How do you resolve Deploying Zowe Server Components on Red Hat OpenShift and Kubernetes for Hybrid Cloud in production? ↓
Offload compute and simplify Zowe administration by running Zowe server components (APIML, Discovery, Desktop, Caching) inside containerized Red Hat OpenShift or Kubernetes clusters while maintaining secure cross-memory connections to z/OS.
How can teams prevent Deploying Zowe Server Components on Red Hat OpenShift and Kubernetes for Hybrid Cloud in enterprise pipelines? ↓
Implement high-availability pod replicas across multiple Kubernetes worker nodes.

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: ZoweKubernetesOpenShiftContainersHybrid CloudModernisation
Diagnostic Runbook Notice & Nominative Fair Use Disclaimer

This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.

IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →

Enterprise Advisory

Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?

StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.