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

Node Instance type Runs

system

m6i.large (2 vCPU, 8 GiB)

Kubernetes add-ons

kfuse

r7i.4xlarge (16 vCPU, 128 GiB)

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.

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.