Choose an AIStore Kubernetes Deployment
AIStore has separate Kubernetes paths for local development and production operator deployments. Choose a path here, then follow its own instructions. For deployments that do not require Kubernetes, refer to Getting Started.
Choose a Path
- Develop and test locally: Use the local KinD or Minikube guide. This operator-less deployment uses
deploy/dev/k8s; it is not a production deployment. Its guide covers the base cluster, access, and ETL-enabled development image. - Plan a production deployment: Start with the ais-k8s production deployment guide and operator guide. The operator manages the AIS cluster lifecycle. Consult its redeployment guide before changing or deleting an existing deployment; cleanup choices can affect cluster state and user data.
Check Prerequisites
For local KinD development, the local Kubernetes guide lists Linux, Docker Engine, KinD, kubectl, and kapp; it also describes the Minikube option. For production, check the ais-k8s prerequisites for Kubernetes and kubectl, node readiness, Linux hosts, drives, and filesystem requirements. The operator guide covers operator installation and webhook certificates. Do not apply local development steps to a production cluster.
Before using the production operator, decide how to provision target storage volumes, configure Kubernetes monitoring, and handle TLS. Follow the upstream deployment guides for the actual manifests and commands.
If the cluster requires authentication, refer to AIS token validation and the operator’s authentication guide and auth profile guide. For an example using an external issuer, refer to the current Keycloak deployment guide. The separate AuthN service guide includes its own security-audit caveat; using the operator does not remove that caveat.
AIStore ETL requires Kubernetes and an ETL-enabled aisnode build or image. The local Kubernetes guide describes its ETL development image; for production, use the ETL prerequisites and operator image guidance before deploying transformations.