Deploy Your First Platform
This guide deploys Floe to a Kubernetes cluster you control. Floe does not require a specific cloud provider for the product path.
Prerequisites
Section titled “Prerequisites”kubectlpoints at the cluster where you want to deploy Floe.helmis installed locally.- You can create namespaces, secrets, services, deployments, jobs, and persistent volume claims.
- You have decided how Floe should access object storage, catalog services, lineage, tracing, and secrets for this environment.
For local evaluation, use Kind. For real deployment, use your organization’s Kubernetes platform and durable backing services.
1. Choose Your Environment
Section titled “1. Choose Your Environment”Use any Kubernetes cluster where you can install Helm charts and create the Floe namespace. Kind is suitable for evaluation. Managed Kubernetes is suitable when your organization supplies durable storage, ingress, TLS, identity, backup, and operational controls.
2. Render The Platform
Section titled “2. Render The Platform”helm dependency update ./charts/floe-platformhelm template floe ./charts/floe-platform \ --namespace floe-dev \ --create-namespace \ >/tmp/floe-platform-rendered.yaml3. Install The Platform
Section titled “3. Install The Platform”helm upgrade --install floe ./charts/floe-platform \ --namespace floe-dev \ --create-namespace4. Wait For Services
Section titled “4. Wait For Services”kubectl get pods -n floe-devkubectl wait --for=condition=Ready pods --all -n floe-dev --timeout=10m5. Draft The Environment Contract
Section titled “5. Draft The Environment Contract”Start from examples/platform-environment-contracts/dev.yaml and replace namespace, release name, registry, access, and URL values for your environment. Keep it in draft until validation confirms the services and access patterns are correct.
6. Validate The Platform
Section titled “6. Validate The Platform”Continue with Validate Your Platform.
7. Prove The Full Demo
Section titled “7. Prove The Full Demo”Run Customer 360 after the basic platform is validated and the Platform Environment Contract is published.