Open Liberty in Kubernetes Hosting on MassiveGRID PaaS
Open Liberty in Kubernetes deploys a Kubernetes cluster on MassiveGRID PaaS with a sample Open Liberty microservice running inside it, exposed through the cluster ingress. Open Liberty is IBM's open-source, cloud-native Java runtime for MicroProfile and Jakarta EE, and this package is the quickest way to run it on Kubernetes.
Open Liberty in Kubernetes on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $78.72 a month for the Starter configuration, a Control plane (2 GiB) and a Worker node (2 GiB), and starts with a 14-day free trial. See the sizing table.
Both buttons open the MassiveGRID PaaS dashboard with Open Liberty in Kubernetes pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
Open Liberty in Kubernetes Package Facts
| Attribute | Value |
|---|---|
| Package | Open Liberty in Kubernetes |
| Type | Application (installs a complete environment) |
| Category | Clusters & Containers |
| Software vendor / project | IBM / Open Liberty project |
| Licence | EPL 2.0 (open source) |
| Runtime / stack | Open Liberty microservice deployed on a Kubernetes cluster with ingress |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use, about $78.72/month for the Starter configuration (32 cloudlets at $0.003372 per cloudlet-hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is Open Liberty in Kubernetes?
Open Liberty is a fast, modular Java runtime that starts in seconds, uses little memory and implements MicroProfile (health, metrics, config, fault tolerance, OpenAPI, JWT) alongside Jakarta EE. It is designed for containers: the runtime and application are built into an image and orchestrated by Kubernetes, with health and metrics endpoints wired to the platform.
The package provisions a Kubernetes cluster (the same topology as the Kubernetes Cluster package), deploys an Open Liberty application as a Kubernetes deployment and service, and routes traffic to it through the ingress controller. It is a working reference you can modify: replace the image with your own Liberty application and the cluster does the rest.
What the Open Liberty in Kubernetes Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure. How these nodes are sized and what they cost.
- Kubernetes cluster: Control plane, auto-scaling workers, ingress controller, dashboard and monitoring.
- Open Liberty deployment: A sample Liberty microservice as a Kubernetes Deployment with a Service and readiness/liveness probes.
- Ingress route: The service exposed over HTTPS on the platform subdomain through the cluster ingress.
- Manifests you can edit: The Kubernetes YAML for the deployment available to adapt for your own application images.
What Open Liberty in Kubernetes Costs to Run
Three starting configurations for the Open Liberty in Kubernetes package, sized in cloudlets (1 cloudlet = 128 MiB RAM + 400 MHz CPU) and priced at the published rate of $0.003372 per cloudlet-hour, or $2.46 per cloudlet-month.
| Configuration | Topology | Cloudlets | Est. per month |
|---|---|---|---|
| StarterDevelopment | Control plane (16 cloudlets, 2 GiB), Worker node (16 cloudlets, 2 GiB) | 32 | $78.72 |
| StandardProduction | Control plane (16 cloudlets, 2 GiB), 2 × Worker node (32 cloudlets, 4 GiB each) | 80 | $196.80 |
| ProductionHA control plane | 3 × Control plane (16 cloudlets, 2 GiB each), 3 × Worker node (48 cloudlets, 6 GiB each) | 192 | $472.32 |
Estimates assume the environment averages the listed cloudlets around the clock; billing is hourly, vertical auto-scaling lowers the figure when the application is idle, and volume discounts apply as usage grows. Disk and external traffic are billed per gigabyte on top. No licence fee applies to the package. Pick a row in the installer by setting the cloudlet limits per node, or start small and let auto-scaling grow it. Price a different topology or a working-hours schedule in the PaaS pricing calculator; the PaaS page describes the billing model.
Why Teams Choose Open Liberty in Kubernetes
Cloud-native Java
MicroProfile health, metrics and config integrate directly with Kubernetes probes and Prometheus.
Fast and lean
Liberty starts in a few seconds and runs with a small footprint, so pods are cheap to scale.
Jakarta EE compatible
Run existing Jakarta EE web-profile applications with minimal change.
Full Kubernetes underneath
Everything from the Kubernetes package: auto-scaling, dashboard, Helm, persistent storage.
How to Install Open Liberty in Kubernetes on MassiveGRID PaaS
Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the Open Liberty in Kubernetes package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every Open Liberty in Kubernetes node, wires them together and hands you the live URL and credentials.
Who Runs Open Liberty in Kubernetes on PaaS
Java microservice platforms
Teams modernising Java EE applications into containerised services.
IBM WebSphere modernisation
Organisations moving from WebSphere to Open Liberty on Kubernetes.
MicroProfile development
Developers building standards-based cloud-native Java with health, metrics and OpenAPI.
Why Run Open Liberty in Kubernetes on MassiveGRID PaaS
Built for uptime. Open Liberty in Kubernetes runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet Open Liberty in Kubernetes environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 27001 and ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: Managed Kubernetes Hosting · Red Hat OpenShift.
Open Liberty in Kubernetes Questions
Open Liberty in Kubernetes Guides from the MassiveGRID Blog
Open Liberty in Kubernetes is covered in these comparison guides and roundups, alongside the packages it is usually deployed with. Browse the blog.
More from the Marketplace
Packages that are often deployed alongside Open Liberty in Kubernetes, or that solve the same problem a different way. Browse all 83 packages.
Deploy Open Liberty in Kubernetes Today
Start the free 14-day trial and have Open Liberty in Kubernetes running in minutes. No credit card required.