OVHcloud releases guide for deploying Microcks on MKS with Gateway API

OVHcloud published on 21 September 2026 a step-by-step guide on its blog for deploying Microcks, an open source API mocking and testing tool, on a Managed Kubernetes Service (MKS) cluster. This is useful for those who need to test an integration when the real backend isn't ready yet, without waiting for the upstream team to release the endpoint.

What you need to get started

The procedure requires an OVHcloud Public Cloud project, API credentials to manage MKS, the OVHcloud CLI, kubectl and Helm. The first step is to create the cluster and a node pool: the Free plan offers a 99.9% SLA and supports clusters up to 100 nodes, but OVHcloud's own guide indicates that for production use it's better to switch to the Standard plan, as Free is intended for testing.

For Microcks, which comprises the application, Keycloak with its PostgreSQL, MongoDB and the Postman runtime, the guide recommends a node pool of three general purpose nodes in b3-8 format (2 vCore, 8 GB RAM). On the official OVHcloud price list that instance costs $0.0605 per hour, roughly $44.165 per month: three nodes for the entire month bring compute alone to over $130 monthly, before storage and networking.

Exposure via Gateway API

To publish Microcks externally the guide uses Gateway API, the successor to Ingress, with Envoy Gateway as the controller and cert-manager paired with Let's Encrypt for automatic TLS certificates. Traffic flows to an OVHcloud Public Cloud Load Balancer. From the official price list, available models range from the S size, Load Balancer S | 200 Mbit/s | 250 | 10000 | | | $0.0095 | ~$6.935, up to XL at $0.2304 | ~$168.192 per month.

LB Size	Bandwidth	Price/month (excl. tax)
S	200 Mbit/s	~$6.935
M	500 Mbit/s	~$17.374
L	2 Gbit/s	~$46.209
XL	4 Gbit/s	~$168.192

The guide configures five listeners on the Gateway: HTTP/HTTPS for Microcks, TLS passthrough for gRPC, HTTP/HTTPS for Keycloak. Microcks is then installed with the official Helm chart, setting gatewayRoutes: true instead of classic Ingress resources.

For those still using the old Load Balancer dedicated to MKS, note this: it has reached End of Sale and End of Support, with End of Life scheduled for July 2026, and must be replaced with the new Public Cloud Load Balancer for all new projects.

For a production environment, OVHcloud finally suggests replacing in-cluster PostgreSQL and MongoDB with their respective Managed Databases services, separating the database from the application platform.