> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/akamas-docs/installing/kubernetes/prerequisites/software-requirements.md).

# Software Requirements

This page describes the requirements that should be fulfilled by the user when installing or managing an Akamas Studio installation on Kubernetes. The software below is usually installed on the user's workstation or laptop.

### Kubectl

Kubectl must be installed and configured to interact with the desired cluster. Refer to the [official kubectl documentation](https://kubernetes.io/docs/tasks/tools/#kubectl) to set up the client.

To interact with the Kubernetes APIs, you will need [kubectl](https://kubernetes.io/docs/tasks/tools/), preferably with a version matching the cluster. To check both the client and cluster versions, run the following:

```bash
kubectl version --short
```

### Helm

Installing Akamas Studio requires [Helm 3.0](https://helm.sh/docs/intro/install/) or higher. To check the version, run the following:

```bash
helm version --short
```

### Privileged access

Akamas Studio uses Elasticsearch to store logs and time series. When running Akamas on Kubernetes, Elasticsearch is installed automatically using the official Elasticsearch helm chart. This chart required running an init container with privileged access to set up a configuration on the Elasticsearch pod host. If running such a container is not permitted in your environment, you can add the following snippet to the `akamas.yaml` file when installing Akamas Studio to disable this feature.

```yaml
# Disable ES privileged initialization container.
elasticsearch:
  sysctlInitContainer:
    enabled: false
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.akamas.io/akamas-docs/installing/kubernetes/prerequisites/software-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.