ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

Studio in Kubernetes: Jib images, liveness and readiness probes, EKS Terraform

Studio and the microservices build images with Jib, answer liveness and readiness probes with component checks, and ship Kubernetes manifests and Terraform for an EKS cluster, on AMD64 and ARM64.

Running the platform in a managed Kubernetes service is mostly a matter of answering the questions the orchestrator asks: are you alive, are you ready, and what image are you. This release answers all three.

Probes

  • Studio Public liveness and readiness endpoints with component checks for the database and for Studio's own readiness.
  • Microservices Health, liveness and readiness endpoints with memory and thread-pool checks.

Images and infrastructure

  • Jib Container images built by the Gradle Jib plugin, with the JVM's container support enabled so resource limits are honoured.
  • Two architectures The microservice base image, with Graphviz, Tesseract and Chrome, builds for AMD64 and ARM64.
  • Manifests and Terraform Deployments, services, ingress, persistent storage and secrets for Studio and Redis; Terraform modules for an EKS cluster, its network and roles; scripts for registry credentials.
  • Configured by environment The default cluster and microservice groups are read from environment variables and validated against the database.

A later release added rootless Podman and Quadlet for estates that run without an orchestrator. This one is for those that have one.