RenderX

IRen InGrid on Kubernetes

Deploy IRen InGrid as a containerized formatting service in Kubernetes — GKE, EKS, AKS, or a private cluster — and scale PDF, PostScript, and AFP output with your workload.

Document formatting workloads are rarely flat. Statement runs, end-of-period reporting, and customer-facing document services arrive in bursts, and capacity sized for the peak sits idle the rest of the time. Kubernetes solves this for stateless services by scaling replicas with demand — and a formatting engine behind a REST API is exactly that kind of service.

The deployment pattern

IRen InGrid runs in Kubernetes clusters — GKE, EKS, AKS, or a private or managed cluster — formatting thousands of pages of PDF, PostScript, AFP, and other supported outputs from customer data through its REST and SOAP APIs. The official renderx/ingrid image on Docker Hub is configured with one formatting engine per container, which maps cleanly onto Kubernetes primitives:

  • A standard Deployment runs the containers; capacity scales by adjusting the replica count to match workload and SLA requirements.
  • A LoadBalancer Service exposes the REST port (6677/tcp) and distributes traffic across healthy pods as the deployment scales.
  • A liveness probe against the REST port restarts unresponsive containers.
  • The production license is supplied through a Secret (it contains sensitive information); engine and grid configuration files are supplied through ConfigMaps.

Clients then POST documents to the /format endpoint — from inside the cluster via the ClusterIP or externally via the assigned external IP — and receive print-ready output in response. IRen InGrid 1.1 (April 2026) consolidated submission on this single /format access point.

Full manifests and step-by-step instructions are in the IRen InGrid documentation. To size a grid for your cluster, contact sales or purchase through the shop.