Managed Kafka and PostgreSQL on OpenShift
OSStend co-manages Kafka and PostgreSQL on the OpenShift cluster you own, in your data center.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ
- ✓Co-managed
- ✓OpenShift
- ✓Kafka and PostgreSQL
Kafka on OpenShift, with PostgreSQL and other engines, is a co-managed OSStend service delivered through an operator on your cluster, with supported charts and images. You keep the platform, the network and the access controls, and OSStend engineers run the data services 24/7.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
Data services on the OpenShift you already run
OpenShift is Kubernetes with extra controls, and the co-managed model is the same as on any Kubernetes cluster. The cluster stays yours, and OSStend designs, moves and runs the data services on it.
The delivery model, the service tier and the SLA type are described on the Kubernetes page. This page covers what is specific to OpenShift.
AceMQ engineers already support customer systems on OpenShift (acemq.com/support, checked 31 Oct 2026). The OpenShift version, the operator and chart version for each engine, and the images are named in the design you sign off.
What is specific to OpenShift
OpenShift applies stricter defaults than plain Kubernetes. The points below are the ones the design step checks first for a database or broker.
| Topic | Why it matters for Kafka and PostgreSQL | Documentation |
|---|---|---|
| Security context constraints | OpenShift controls what a pod may run as and which volume types it may use through security context constraints. An image or chart written for plain Kubernetes may need to fit those rules. | OpenShift security context constraints |
| Rack and zone awareness | Kafka can place replicas by rack, which maps to zones on a multi-zone cluster. Replica placement is part of the broker and partition plan. | Kafka broker.rack |
| Storage | Both engines depend on persistent volumes that perform predictably. | Persistent volumes |
| Disconnected clusters | Some OpenShift clusters have no internet route. The delivery then follows the air-gapped model. | See air-gapped |
Documentation links checked 30 Oct 2026.
Kafka and PostgreSQL on OpenShift
Kafka and PostgreSQL are the engines most teams put on OpenShift first. Each page covers the sizing and the tailoring for that engine.
- Managed Kafka: broker count and partition plan designed for your estate, with change data capture for downstream systems.
- Managed PostgreSQL: any size and replica layout, with the extensions you need, run through CloudNativePG.
- Other engines are listed on managed database services. All three places a cluster can run are compared on deployment options.
When it fits and when it does not
This option suits teams that have standardised on OpenShift and want the data services run by specialists.
Contact us if
- ✓OpenShift is your platform standard, in your data center, and a residency rule keeps the data there. See data residency and sovereign deployments.
- ✓You want Kafka or PostgreSQL on it without adding an on-call burden for your platform team.
Not a fit if
- ✕You do not run OpenShift and want the cluster hosted for you. See bring your own cloud.
- ✕Your workload fits a standard plan, where a turnkey service costs less.
FAQ
Can Kafka run on OpenShift?
Yes. Kafka runs on OpenShift with persistent volumes, rack-aware replica placement and a broker and partition plan sized to the workload. OSStend runs it there as a co-managed service.
Is the service fully managed on OpenShift?
No. On a customer-owned OpenShift cluster the service is co-managed: the customer keeps the platform, and OSStend runs the data services under a response-time SLA.
Does OpenShift change how PostgreSQL is delivered?
The delivery is the same operator, charts and images as on Kubernetes, and the PostgreSQL operator is CloudNativePG (details). OpenShift adds security context constraints, which the design step checks before anything is built.
Related pages
- Deployment · Your data centerPostgreSQL on Kubernetes, managed by OSStendRun PostgreSQL on Kubernetes and Kafka on your own cluster, co-managed by OSStend through an operator with supported charts and images, 24/7.
- Deployment · Air-gappedAir-gapped cloud and on-prem managed open sourceAir-gapped cloud and on-prem sites: OSStend co-manages PostgreSQL, Kafka and RabbitMQ on infrastructure you own, with hardened FIPS editions on request.
- KafkaManaged Kafka in your cloud or data centerManaged Kafka with the broker count, partition plan, KRaft, Connect and schema registry designed for your estate, run 24/7 in your cloud or your data center.
- PostgreSQLManaged PostgreSQL service and Postgres hostingManaged PostgreSQL service, compared: how to choose between RDS, Aiven, Crunchy Bridge, Neon and a tailored cluster run 24/7 in your cloud or ours.
- Deployment · CloudNativePGManaged CloudNativePG: Postgres on your KubernetesCloudNativePG run for you on your own Kubernetes or OpenShift: high availability, backups, upgrades and 24/7 operations by OSStend engineers.
- EnginesManaged database service for enterprise workloadsA managed database service for enterprise workloads: PostgreSQL, MySQL, Redis or Valkey, OpenSearch and Kafka, designed, run and tuned by engineers.
Talk to an engineer about OpenShift
Bring your OpenShift version, the engines you want and where it runs. An engineer will review them with you and sketch the design in 45 minutes.
- ✓A design sketch for your workload, not a plan menu
- ✓A zero-downtime cutover path for what you run today
- ✓A price for that design, after the review