> For the complete documentation index, see [llms.txt](https://documentation.planeo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.planeo.dev/getting-started/requirements.md). # Requirements Let's start by deploying your application using Planeo. ### Prerequisites Before using Planeo, ensure that all the below required dependencies are installed and properly configured on your system: * Docker is installed and running * Logged into docker registry if you need to [update containers](https://documentation.planeo.dev/configuration-of-services/updating-containers) * Kubectl is installed ### Requirements Before you start you will need the following * A Helm chart, either in a local folder, or via a remote Helm repo (oci is not currently supported) * A connection to any Kubernetes cluster (if kubectl works you should be good to go) * The `planeo` cli running ### Setting up test cluster While in many cases you'll want to test on your remote cluster, perhaps in your dev or staging environment, you can quickly start using Planeo with a local cluster. Kind is one of many options to set up a testing cluster, follow the [getting started docs](https://kind.sigs.k8s.io/docs/user/quick-start/) for details on how to set up a kind cluster. Other options include * minikube * k3s * docker desktop * microk8s ### Test Charts While trying out a tool like Planeo, it can be helpful to have some test charts to experiment with. Here are some good candidates: * - A good simple chart to simply have a payload to deploy * - A set of testing microservices we set up to demonstrate some of the capabilities of Planeo. Along with a Helm chart you will also need to make sure that the Kubernetes cluster has access to the images used in the Helm chart, which could require [pushing them to a local registry.](https://minikube.sigs.k8s.io/docs/handbook/pushing/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://documentation.planeo.dev/getting-started/requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.