Deploy Generic Control Plane

​

Key Components

• TrueFoundry Control Plane (Shipped as a helm chart called truefoundry)
• PostgreSQL Database (Managed or Self-Hosted with PostgreSQL >= 13)
• Blob Storage (S3, Minio, or any other S3 compatible storage)

​

Compute Requirements

​

Prerequisites for Installation

1. Kubernetes Cluster: K8s cluster 1.27+ with minimum 4vCPU and 8GB RAM.
2. Support for dynamic provisioning of storage for PVC (such as local storage provisioners, Longhorn, OpenEBS, or other on-premises storage solutions) and support for exposing the control plane dashboard via:
   • Ingress controller (e.g., Nginx Ingress Controller), or
   • Istio service mesh
3. Domain to map the ingress of the Control Plane dashboard along with certificate for the domain.
   This Domain will be referred as Control Plane URL in our documentation.
4. Egress access to TrueFoundry Central Auth Server:
   • https://auth.truefoundry.com
   • https://login.truefoundry.com
5. Tenant Name, Licence key, and image pull secret from TrueFoundry team. If you have not registered yet, please visit TrueFoundry to register.
6. PostgreSQL database (version >= 13). We recommend managed PostgreSQL database for production environments. For instance requirements, refer to the Compute Requirements section.
   In case you do not have a managed database for testing purposes, set devMode to true in the values file to spin up a local PostgreSQL database.
7. Blob Storage to store artifacts and logs (S3, Minio, or any other S3 compatible storage).

​

Installation Instructions

helm repo add argo https://argoproj.github.io/argo-helm
helm repo update argo

helm install argocd argo/argo-cd \
--namespace argocd \
--create-namespace \
--version 7.8.26 \
--set server.extraArgs[0]="--insecure" \
--set server.extraArgs[1]="--application-namespaces=*" \
--set controller.extraArgs[0]="--application-namespaces=*" \
--set applicationSet.enabled=false \
--set notifications.enabled=false \
--set dex.enabled=false

apiVersion: v1
kind: Secret
metadata:
  name: truefoundry-creds
type: Opaque
stringData:
  TFY_API_KEY: <TFY_API_KEY> # Provided by TrueFoundry team
  DB_HOST: <DB_HOST>
  DB_NAME: <DB_NAME>
  DB_USERNAME: <DB_USERNAME>
  DB_PASSWORD: <DB_PASSWORD>

kubectl apply -f truefoundry-creds.yaml -n truefoundry

apiVersion: v1
kind: Secret
metadata:
  name: truefoundry-image-pull-secret
type: kubernetes.io/dockerconfigjson
data:
  .dockerconfigjson: <IMAGE_PULL_SECRET> # Provided by TrueFoundry team

kubectl apply -f truefoundry-image-pull-secret.yaml -n truefoundry

global:
  # Domain to map the control plane dashboard
  controlPlaneURL: https://truefoundry.example.com

  # Ask TrueFoundry team to provide these
  tenantName: <TENANT_NAME>

  # Choose the resource tier as per your needs
  resourceTier: medium # or small or large

  # This is the reference to the secrets we created in the previous step
  existingTruefoundryCredsSecret: "truefoundry-creds"
  imagePullSecrets:
  - name: "truefoundry-image-pull-secret"
  ## Add if you have restricted public registry access
  # image:
  #   pullSecretNames: 
  #   - "truefoundry-image-pull-secret"

  config:
    defaultCloudProvider: "aws"
    storageConfiguration:
      # Use the blob storage configuration from "Setup Blob Storage" step
      awsS3BucketName: "<S3_BUCKET_NAME>"
      awsRegion: "<S3_REGION>"
      # For S3-compatible storage (Minio, etc.), provide credentials and endpoint
      awsAccessKeyId: "<AWS_ACCESS_KEY_ID>"
      awsSecretAccessKey: "<AWS_SECRET_ACCESS_KEY>"
      awsEndpointURL: "<AWS_ENDPOINT_URL>" # e.g., http://minio.example.com
      # awsAllowHttp: "true" # Optional: Enable if using HTTP instead of HTTPS
      
      # Alternative: Use Kubernetes secret for credentials (recommended for production)
      # awsAccessKeyId: ${k8s-secret/truefoundry-creds/AWS_ACCESS_KEY_ID}
      # awsSecretAccessKey: ${k8s-secret/truefoundry-creds/AWS_SECRET_ACCESS_KEY}

# In case, you want to spin up PostgreSQL on kubernetes, enable this
# Please add creds and host details in the secret `truefoundry-creds`
devMode:
  enabled: false

truefoundryFrontendApp:
  ingress:
    hosts:
      - truefoundry.example.com # Replace with your domain (without https://)
    enabled: false
    annotations: {}
    ingressClassName: nginx # Replace with your ingress class name

# Enable AI Gateway features
tags:
  llmGateway: true
  llmGatewayRequestLogging: true

helm upgrade --install truefoundry oci://tfy.jfrog.io/tfy-helm/truefoundry \
-n truefoundry --create-namespace -f truefoundry-values.yaml

kubectl get svc -n truefoundry

kubectl get pods -n argocd
kubectl get pods -n truefoundry

​

Setting Up Compute Plane

​

Configuring Node Pools for TrueFoundry

​

Node Pool Label Configuration

1. Click on edit in the Cluster and then toggle on the Advanced Fields section.
2. Under Node Label Keys, fill in the Nodepool Selector Label with your chosen label key.

​

GPU Node Pool Configuration

• A10G, A10_12GB, A10_24GB, A10_4GB, A10_8GB
• A100_40GB, A100_80GB
• H100_80GB, H100_94GB, H200
• L4, L40S
• P100, P4, T4, V100

​

Adding Domain for Workloads

1. Add a separate domain for hosting workloads (can be a wildcard domain).
2. Point the domain to the load balancer IP address.
3. Configure TLS certificate for the domain.
4. Add the domain in the TrueFoundry platform UI.

​

Adding Docker Registry