Release notes
v25.1
Self-managed Materialize is available as a paid Enterprise Edition and a free Community Edition:
Enterprise Edition | Community Edition | |
---|---|---|
Maximum Usage Limits (Memory) | None | 24 GiB |
Maximum Usage Limits (Disk) | None | 48 GiB |
Support | Per terms of your license | Community slack |
License | Paid Enterprise License - Contact Us | BSL/Privacy Policy |
Materialize Operator
For self-managed deployments, Materialize provides the Materialize Operator. The Materialize Operator manages Materialize environments within your Kubernetes infrastructure.
Materialize provides the Materialize Operator Helm Chart, a Helm
Chart for installing and upgrading the
Materialize Operator. The chart
repository is:
https://materializeinc.github.io/materialize
.
Releases and Compatibility
Materialize Operator | orchestratord version | environmentd version |
---|---|---|
v25.1.2 | v0.130.4 | v0.130.4 |
Terraform helpers
To help you get started, Materialize also provides some template Terraforms.
These modules are intended for evaluation/demonstration purposes and for serving as a template when building your own production deployment. The modules should not be directly relied upon for production deployments: future releases of the modules will contain breaking changes. Instead, to use as a starting point for your own production deployment, either:
-
Fork the repo and pin to a specific version; or
-
Use the code as a reference when developing your own deployment.
Sample Module | Description |
---|---|
terraform-helm-materialize | A sample Terraform module for installing the Materialize Helm chart into a Kubernetes cluster. |
Materialize on AWS | A sample Terraform module for deploying Materialize on AWS Cloud Platform with all required infrastructure components. See Install on AWS for an example usage. |
Materialize on Azure | A sample Terraform module for deploying Materialize on Azure with all required infrastructure components. See Install on Azure for an example usage. |
Materialize on Google Cloud Platform (GCP) | A sample Terraform module for deploying Materialize on Google Cloud Platform (GCP) with all required infrastructure components. See Install on GCP for an example usage. |
Terraform version | Notable changes |
---|---|
v0.4.0 |
|
v0.3.1 |
|
v0.3.0 |
|
v0.2.7 |
|
If upgrading from a deployment that was set up using an earlier version of the Terraform modules, additional considerations may apply when using an updated Terraform modules to your existing deployments.
See also Upgrade Notes for release-specific upgrade notes.
Terraform version | Notable changes |
---|---|
v0.3.1 |
|
v0.3.0 |
|
v0.2.0 |
|
v0.1.4 |
|
If upgrading from a deployment that was set up using an earlier version of the Terraform modules, additional considerations may apply when using an updated Terraform modules to your existing deployments.
See also Upgrade Notes for release specific notes.
Terraform version | Notable changes |
---|---|
v0.3.0 |
|
v0.2.0 |
|
v0.1.7 |
|
If upgrading from a deployment that was set up using an earlier version of the Terraform modules, additional considerations may apply when using an updated Terraform modules to your existing deployments.
See also Upgrade Notes for release specific notes.
Known Limitations
Item | Status |
---|---|
IAM Built-in authorization mechanisms. |
In progress |
License Compliance License key support to make it easier to comply with license terms. |
In progress |
Spill to disk Provide Terraform modules to set up locally-attached NVMe storage to support workloads that are larger than can fit into memory. |
|
Ingress from outside cluster Provide Terraform modules to set up ingress from outside the Kubernetes cluster hosting self-managed Materialize. |
|
AWS Connections AWS connections require backing cluster that hosts Materialize to be AWS EKS. |
|
EKS/Azure Connections | |
Temporal Filtering Memory optimizations for filtering time-series data are not yet implemented. |
Self-managed versioning and lifecycle
Self-managed Materialize uses a calendar versioning (calver) scheme of the form
vYY.R.PP
where:
YY
indicates the year.R
indicates major release.PP
indicates the patch number.
For Self-managed Materialize, Materialize supports the latest 2 major releases.