Environment & requirements

To keep Loambase Foundry running stably inside your private environment (IDC or VPC) while handling massive datasets, have your IT department confirm the following hardware, software and network requirements before deployment.

1. Hardware requirements

The platform’s hardware consumption depends on the data volume you need to process and the number of concurrent pipeline tasks. Recommended configurations by scale:

1.1 Minimal PoC environment

For proofs of concept, dev/testing or small data volumes (up to tens of millions of rows).

• Compute node: 1
• CPU: 8 vCPUs
• Memory: 32 GB RAM
• Storage: 500 GB SSD (for the database and local lake storage)

1.2 Standard production environment

For serious enterprise use, with high availability (HA) and high-concurrency data processing.

• Master nodes: 3 (4 cores / 16 GB)
• Worker nodes: at least 3, supporting horizontal auto-scaling
  • Per-node recommendation: 16 cores / 64 GB RAM
• Storage:
  • PostgreSQL requires enterprise-grade SSDs or mounted cloud disks.
  • For the Iceberg lake, we strongly recommend an external S3-compatible object store (MinIO, AWS S3, Tencent COS, etc.) instead of local disks.

2. Software requirements

Loambase Foundry ships as cloud-native containerized assets; the target environment must provide a standard Kubernetes runtime.

• Kubernetes version: v1.24 or later. Standard K8s or managed clusters (EKS, TKE, ACK, etc.) both work. Without an existing cluster, we recommend standing one up on bare metal with RKE2 or K8s.
• Package management: Kustomize (v4+) or Helm (v3+).
• Ingress controller: the cluster must have ingress-nginx preinstalled.
• Container runtime: containerd or docker.

3. Network & security requirements

3.1 Open ports

Cluster nodes must expose the following ports to the intranet (or specific office network segments):

• 80 (HTTP) and 443 (HTTPS): platform web access and APIs.
• 6443: (optional) the Kubernetes API server port, for the delivery team to run deployment scripts.

3.2 Domain & certificates (TLS)

The platform requires HTTPS; plain HTTP deployment is not supported.

• Prepare a wildcard certificate (e.g. *.foundry.yourcompany.com).
• Inject it as a Kubernetes Secret (type kubernetes.io/tls) into the namespace where Ingress lives.
• If your enterprise has no commercial certificate yet, we can deploy cert-manager inside the cluster and let Let’s Encrypt issue and renew automatically.

3.3 Network connectivity (VPC peering)

For the platform to pull your business data, the VPC hosting the Kubernetes cluster must be able to reach:

1. Source databases: your MySQL, Oracle or ERP systems and their APIs.
2. Enterprise identity directory: the existing LDAP/AD domain controller (if bridging with the platform’s bundled Keycloak).