Managed PostgreSQL and Kafka on your Kubernetes or OpenShift
OSStend co-manages PostgreSQL, Kafka and other engines on the Kubernetes or OpenShift cluster you own, through an operator with supported charts and images.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ
- ✓Co-managed
- ✓Kubernetes and OpenShift
- ✓Operator, charts and images
PostgreSQL on Kubernetes, with Kafka and other engines, is a co-managed OSStend service on your Kubernetes or OpenShift cluster. It is delivered through an operator on your cluster, with supported charts and images. You keep the infrastructure, the network and the access controls.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
What co-managed means on your cluster
Co-managed is the tier for clusters you own. The infrastructure and the network stay yours, and OSStend engineers design, move and run the data services on top, under a response-time SLA.
| Your Kubernetes or OpenShift | Dedicated or your cloud account | |
|---|---|---|
| Service tier | Co-managed | Fully managed |
| Who owns the infrastructure | You | OSStend, or you in your account |
| Network and access controls | Yours | Set in the design, or yours |
| Kind of SLA | Response-time SLA | Uptime SLA |
| How it is delivered | An operator on your cluster, with supported charts and images | OSStend runs the cluster |
Terms for each tier are on service levels. The three options side by side are on deployment options.
Operators, charts and images
On Kubernetes a database or broker is usually run by an operator: a controller that watches a custom resource and keeps the cluster in the state it describes. OSStend delivers its service through an operator on your cluster, with supported charts and images.
The pattern is documented by Kubernetes as the operator pattern, and stateful engines run as StatefulSets with persistent volumes. Community operators exist for the main engines, for example CloudNativePG for PostgreSQL, Strimzi for Kafka and the RabbitMQ Cluster Operator. They show what an operator manages. For PostgreSQL, OSStend runs CloudNativePG; see managed CloudNativePG (project links checked 30 Oct 2026).
The Kubernetes version and distribution, the operator and chart version for each engine, and the images it runs are named in the design you sign off, so the supported set is the one written down for your cluster.
What the design step settles
Running a stateful engine on Kubernetes comes down to a few platform choices. They are set in the cluster design you sign off, before anything is built.
| Question | Why it matters | Kubernetes documentation |
|---|---|---|
| Storage | Databases and brokers need volumes that outlive a pod and perform predictably. | Persistent volumes |
| Spread across zones and nodes | Replicas on one node or one zone fail together. | Topology spread constraints |
| Planned disruption | Node upgrades drain pods, and a quorum-based engine must not lose too many at once. | Pod disruption budgets |
| Network isolation | Which workloads and operators may reach the data services. | Network policies |
| Upgrade calendar | Operator, engine and node upgrades follow your change windows, not a fixed schedule. | Set in the design; see how it works |
Kubernetes documentation links checked 30 Oct 2026.
Engines on your cluster
PostgreSQL and Kafka are the usual starting points, and the other engines follow the same delivery model.
- Managed PostgreSQL: any size and replica layout, with the extensions you need.
- Managed Kafka: broker count and partition plan designed for your estate.
- Managed CloudNativePG: PostgreSQL on your cluster through the CloudNativePG operator.
- RabbitMQ hosting, managed Redis or Valkey, managed MySQL, managed MongoDB and managed OpenSearch.
- Running on Red Hat OpenShift? See Kafka and PostgreSQL on OpenShift.
When it fits and when it does not
Co-managed on Kubernetes fits teams that have a platform they trust and want the data services run by engineers who do it all day.
Contact us if
- ✓You run Kubernetes or OpenShift in your data center and want to keep it there, for example under a residency or sovereignty rule.
- ✓Cloud repatriation is on the roadmap and the data services have to move with it.
- ✓Your platform team owns the cluster but does not want to be on call for databases and brokers.
Not a fit if
- ✕You want the whole stack, including the infrastructure, run for you. See bring your own cloud or the fully managed tiers.
- ✕Your workload fits a standard plan, where a turnkey service costs less.
FAQ
Can PostgreSQL run on Kubernetes in production?
Yes, with an operator that manages replicas, failover and backups, and with storage, zone spread and upgrade windows planned up front. OSStend delivers PostgreSQL on a customer's Kubernetes through the CloudNativePG operator, with supported charts and images. See managed CloudNativePG.
Who is on call when the cluster is mine?
In the co-managed tier OSStend engineers run the data services 24/7 under a response-time SLA. The customer's team stays responsible for the underlying infrastructure and network.
Does it work on OpenShift?
Yes. OpenShift is a supported platform for the co-managed tier. The OpenShift-specific points are on the OpenShift page.
Related pages
- Service levelsService levels: two tiers, a written SLAOSStend service levels: fully managed and co-managed tiers, what each one covers, who is on call and how incidents are handled, with a written SLA for each.
- DeploymentManaged databases: our cloud, yours or on-premManaged databases in OSStend's cloud, your AWS, Azure or Google Cloud account, or your data center. PostgreSQL, Kafka and RabbitMQ, run 24/7 by engineers.
- 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.
- How it worksHow OSStend works: design, move, runOSStend designs your cluster around the workload, moves it in with zero downtime and runs it 24/7. See the three steps and what turnkey services leave out.
- 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.
- 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.
Talk to an engineer about your cluster
Bring the platform you run and the engines you want on it. 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