> For the complete documentation index, see [llms.txt](https://kandola.girnaartech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kandola.girnaartech.com/introduction.md).

# Introduction

The instructions in this section describe how to become a storage node operator and orchestrate your infrastructure automatically for a Kandola Node Operator for:

1. Automated bidding with dynamic pricing engine
2. Infrastructure orchestration through Kubernetes
3. Cluster creation and infrastructure management
4. Automated infrastructure allocation and connection back to Kandola network
5. Monitoring
6. Infrastructure life cycle management.

This section assumes you are aware of Kandola's basic architecture. If not, you can learn more about the different types of nodes, roles, responsibilities and opportunities of a storage node operator in Kandala docs here.

The following section is created and maintained by Girnaar Nodes, a launch partner and Node Operator Committee Evanlegizer for Kandola.

If you have issues using the instructions in the section below or if you like to contribute, or simply connect you can get in touch with us here.

Telegram

Discord


---

# 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:

```
GET https://kandola.girnaartech.com/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.