POC Terraform Resources
On a new cluster, Terraform creates these resources in your cloud account. ./uninstall.sh deletes them. On an existing cluster, Terraform isn’t used and nothing on this page is created.
Resources by cloud
-
AWS
-
Google Cloud
-
Azure
| Node | Instance type | Runs |
|---|---|---|
system |
|
Kubernetes add-ons |
kfuse |
|
Kloudfuse |
What gets created, all in the region and tagged kfuse-poc=true:
-
A VPC with two public and two private subnets, an internet gateway, and a NAT gateway. The nodes have no public IPs.
-
The EKS cluster
<cluster_name>, with a public API endpoint, and the two nodes. The Kloudfuse node is in the region’s first availability zone. -
IAM roles for the cluster, the nodes, and the EBS disk driver.
-
gp3 EBS volumes for Kloudfuse data.
-
The S3 bucket
<cluster_name>-<account id>-deepstore, for Kloudfuse data, the log archive, and RUM recordings. -
The Elastic IP
<cluster_name>-ingress, for the Network Load Balancer that the Kloudfuse Envoy gateway creates.
| Node | Machine type | Runs |
|---|---|---|
system |
|
Kubernetes add-ons |
kfuse |
|
Kloudfuse |
What gets created, all in your project and labelled kfuse-poc=true where Google Cloud supports labels:
-
The VPC
<cluster_name>-vpcwith one subnet, a Cloud Router, and Cloud NAT. The nodes have no public IPs. -
A zonal GKE cluster with a public API endpoint, and the two nodes, with the service account
<cluster_name>-nodes. -
Hyperdisk Balanced disks for Kloudfuse data.
-
The storage bucket
<project_id>-<cluster_name>-deepstore, for Kloudfuse data, the log archive, and RUM recordings. -
The static IP
<cluster_name>-ingress, for the load balancer that the Kloudfuse Envoy gateway creates.
| Node | VM size | Runs |
|---|---|---|
system |
|
Kubernetes add-ons |
kfuse |
|
Kloudfuse |
The v5 sizes are used where your subscription allows them, and the v7 sizes otherwise. Some credit and trial subscriptions block v5.
What gets created, all in the resource group <cluster_name>-rg and tagged kfuse-poc=true:
-
A VNet with a node subnet and a NAT gateway with its own public IP. The nodes have no public IPs.
-
The AKS cluster
<cluster_name>(Free tier), with a public API endpoint, and the two nodes, both in the chosen zone. -
A managed identity for the cluster, and the nodes' identity.
-
Premium SSD v2 disks for Kloudfuse data.
-
A storage account named from the cluster name plus a short suffix, with
kfuseandrumcontainers. -
The static public IP
<cluster_name>-ingress, for the load balancer that the Kloudfuse Envoy gateway creates.
install.sh then creates the Kubernetes objects inside the cluster: the namespace, Secrets, the kloudfuse-disk storage class, the Gateway API CRDs, cert-manager (for Let’s Encrypt only), and Kloudfuse.