Appendix: Terraforms

To help you get started, Materialize provides some template Terraforms.

! Important:

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.

Releases

Materialize on AWS Terraform module

Terraform version	Notable changes
v0.4.3	Defaults to using Materialize Operator v25.1.7 (via `terraform-helm-materialize` v0.1.12). Versions v0.4.0 defaulted to Materialize Operator v25.1.6 which used an incorrect version of the `orchestratord`).
v0.4.0	By default, deploys `cert-manager` and a self-signed `ClusterIssuer`.
v0.3.1	By default, deploys OpenEBS and NVMe instance storage to enable spill-to-disk.
v0.3.0	By default, deploys the AWS Load Balancer Controller as well as Network Load Balancers (NLBs) for each Materialize instance (i.e., the `create_nlb` flag defaults to `true`). The NLBs, by default, are configured to be internal (i.e., the `internal_nlb` flag defaults to `true`).
v0.2.7	Initial release of Materialize on AWS.

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.

Materialize on Azure Terraform module

Terraform version	Notable changes
v0.3.4	Defaults to using Materialize Operator v25.1.7 (via `terraform-helm-materialize` v0.1.12). Version v0.3.1 defaulted to Materialize Operator v25.1.6 which used an incorrect version of the `orchestratord`).
v0.3.1	By default, deploys load balancers for each Materialize instance (i.e., the `create_load_balancer` flag defaults to `true`). The load balancers, by default, are configured to be internal (i.e., the `internal_load_balancer` flag defaults to `true`).
v0.3.0	By default, deploys `cert-manager` and a self-signed `ClusterIssuer`.
v0.2.0	The providers must be specified. The `examples/simple/main.tf` has been updated to reflect this. The network_config is now a required input. Previously, a default value was provided. The `examples/simple/main.tf` has been updated to reflect this.
v0.1.4	Initial release of Materialize on Azure.

Materialize on GCP Terraform module

Terraform version	Notable changes
v0.4.0	By default, deploys OpenEBS and NVMe instance storage to enable spill-to-disk. Associated with this change, the default `gke_config.machine_type` has changed from `e2-standard-4` to `n2-highmem-8`.
v0.3.4	Defaults to using Materialize Operator v25.1.7 (via `terraform-helm-materialize` v0.1.12). Versions v0.3.0-v0.3.3 defaulted to Materialize Operator v25.1.6 which used an incorrect version of the `orchestratord`.
v0.3.1	Added configuration options (`storage_bucket_versioning` and `storage_bucket_version_ttl`) for storage bucket versioning. By default, versioning is disabled (i.e., `storage_bucket_versioning` is set to `false`).
v0.3.0	By default, deploys `cert-manager` and a self-signed `ClusterIssuer`. By default, deploys load balancers for each Materialize instance (i.e., the `create_load_balancer` flag defaults to `true`). The load balancers, by default, are configured to be internal (i.e., the `internal_load_balancer` flag defaults to `true`). The network_config variable no longer has a default value. Previously, a default value was provided.
v0.2.0	The providers must be specified. The `examples/simple/main.tf` has been updated to reflect this.
v0.1.7	Initial release of Materialize on GCP.