Deploying on Kubernetes
Last updated
Last updated
is an open-source platform for managing containerized applications and workloads across clusters of servers. It automates the deployment, scaling, and orchestration of containers, and provides declarative configuration and automation features.
In order to get started, you will need to have a working Kubernetes cluster. You can get a local Kubernetes cluster for testing using a tool like .
The is available in the official Docker repository, and it is available in an always up-to-date tag (curiosityai/curiosity:latest
) and a versioned tag (curiosityai/curiosity:VERSION
)
Curiosity Workspace can be deployed using Docker images on Kubernetes. To run Curiosity on Kubernetes, you needto use a StatefulSet with attached persistent storage. A StatefulSet is a Kubernetes resource that provides stable and unique identities for each pod in the set. Attached storage is a way of providing persistent and durable data volumes for the pods. By using a StatefulSet with attached storage, users can ensure that Curiosity Workspace maintains its state and data across pod restarts and updates.
A typical YAML configuration for such deployment looks like below. Please refer to the for the version of your cluster for more information.
Configure Curiosity using environment variables in the template.spec.containers.env
section of the deployment configuration. See for a list of all configurable variables. If not set via configuration variables, the username and password for your first log is admin
. You can now follow the steps under .
You can define a for the admin account, and pass it using an environmental variable. You can store this as a in Kubernetes.