Installation Requirements
Datastrato Enterprise is deployed on Kubernetes. There is no tarball install, no Docker Compose path, and no bare-metal path. One deployment artifact means one thing to test, support, and upgrade.
Cluster
| Requirement | Minimum |
|---|---|
| Kubernetes | 1.29 or later |
| Helm | 3.8 or later, for OCI registry support |
| CPU | 2 cores available to the Gravitino pod |
| Memory | 4 GiB available to the Gravitino pod |
| Storage | A default storage class, unless you supply persistent volumes yourself |
Managed Kubernetes on any cloud works, as does a self-managed cluster. Helm earlier than 3.8 cannot pull from an OCI registry and will fail at the first step.
Registry Access
The chart and the container images are served from the same OCI registry. Nodes must be able to pull images from it, and whatever machine runs Helm must be able to reach it.
Air-gapped clusters mirror the registry into an internal one. Because the chart and the images live together, one mirroring operation covers both, and relocating them keeps them in step.
Storage Backend
Gravitino stores its own entities in a relational backend. The chart can deploy one for you, which is appropriate for evaluation and not for production.
For production, supply an existing database. Size it for metadata rather than for data: the entity store holds catalog definitions, tags, policies, and grants, not table contents.
Network
The server listens on 8090 for the API and the UI. Auxiliary services listen on their own ports, including SCIM on 9201 when enabled.
Every connected source must be reachable from the Gravitino pods. A catalog whose database sits behind a firewall the cluster cannot cross fails at creation, since the connection is tested before the catalog is committed.
If you provision users from an identity provider over SCIM, that endpoint must be reachable from the provider's cloud over HTTPS with a publicly trusted certificate. See SCIM provisioning.
Java and Client Requirements
The server runs inside the container image and needs nothing installed on the host.
The Java client requires Java 17 or later. The Python client requires Python 3.10 or later. Engine connectors have their own version requirements, listed with each connector.
License
A license key is required. The server starts without one and refuses to serve requests, so an install that appears healthy but rejects everything is usually a licensing problem rather than a configuration one. See Licensing.