Menu

1 / 4

Why My Microservices Broke on OpenShift — And How a Hidden Kubernetes Quota Nearly Cost Me Days

DEV Community·Anupam Kushwaha·6 months ago
#ZSVLJPaT
#bug#fix#gateway#kubernetes#quota
Reading 0:00
15s threshold

Deploying four Spring Boot microservices to OpenShift Developer Sandbox, I hit two silent failures — a ReplicaSet quota exhaustion and a gateway routing to localhost. Here is the full debugging story.

If you're deploying microservices on OpenShift's free Developer Sandbox (or any resource-constrained Kubernetes cluster), this post might save you hours of debugging.

The Setup

I built a production-grade mobile application backed by a microservices architecture — four Spring Boot services deployed to Red Hat OpenShift Developer Sandbox via a fully automated GitHub Actions CI/CD pipeline .

The stack:

Flutter mobile frontend (automated APK releases)

API Gateway (Spring Cloud Gateway) — single entry point for all client requests

Auth Service — handles registration, login, OTP verification, JWT tokens

User Service — user profiles, preferences, settings

Core Service — main business logic, AI features, data processing

MongoDB Atlas — separate databases per service

GitHub Container Registry (GHCR) — Docker…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.