Infrastructure and Setup FAQs

How do I get started with the infrastructure setup on Truefoundry?

TrueFoundry's platform runs on Kubernetes, featuring a control plane and a compute plane. For more details on TrueFoundry's architecture, click here.

TrueFoundry offers a hosted multi-tenant control plane that orchestrates deployments across multiple compute planes. You can create a Kubernetes cluster in your own cloud account and connect it to the hosted control plane by installing the tfy-agent in your Kubernetes cluster. This ensures that all compute and data remain within your own cloud environment.

For enterprises, we recommend hosting both the control plane and the compute plane in your own cloud environment.

You can go through our setup guide and reach out to [email protected] if you need any assistance to set up your cluster.

Refer to the guide below for setting up the compute plane with your cloud provider -

AWS - https://docs.truefoundry.com/docs/infrastructure-requirements

GCP - https://docs.truefoundry.com/docs/infrastructure-requirements-gcp

Azure - https://docs.truefoundry.com/docs/infrastructure-requirements-azure

Do we have a way to get on-prem machines on TrueFoundry?

Yes, you can set up on-premises machines by installing Kubernetes on them, which will allow them to be integrated into our system. Additionally, you can install k3s, a lightweight version of Kubernetes, for easier setup and lower resource usage. Once installed, these machines can be configured and tested to ensure seamless integration and efficient management

Is there a cost for integrating clusters without any active workloads?

If the clusters are running, there is a constant cost of around $150 to keep the cluster running. The cost stems from a fixed $75 for Kubernetes charged by the cloud providers and the rest is for running a couple of nodes to run the core components like ArgoCD, Prometheus, Loki, etc.

Why is it important to set up a domain to map to the cluster load balancer?

When we deploy applications using truefoundry, they need to have a DNS mapping so that we can access the API endpoints. This is also needed for starting hosted notebooks. For this, it's important to map a domain to the load balancer IP.

How do we use extra cloud credits for cross-cloud services?

You can use additional credits from another cloud provider to leverage cross-cloud services for efficient workload migration and cost savings. This process is straightforward with Truefoundry. You can easily create a cluster in the new cloud account, connect it to the control plane, and simply clone the workloads.

Getting 'InitAWS: Not able to authenticate to profile' error with OCLI.

If you get this error InitAWS: Not able to authenticate to profile <profile-name> when running an ocli commands. Make sure you have aws cli installed and configured as stated here.

Also make sure you runaws configure to configure your environment to work with ocli. The credentials and config file are created/updated when you run the aws configure command. The credentials file stores credential information for the configured profiles and is located at ~/.aws/credentials. The config file is intended for storing non-sensitive configuration options for the configured profiles and is located at ~/.aws/config. These files can also be created manually but it is recommended to use the aws cli.

Further information on how to configure your AWS credentials on your device can be found here - https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html.

One important thing to note is that ocli works only with AWS profiles, setting only AWS environment variables won't work.