> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/floating-server/floating-server-v1/deployment-methods/kubernetes-helm/installation-steps.md).

# Installation Steps

{% stepper %}
{% step %}

### Download the Helm Chart

Get the Helm chart from [**Artifact Hub**](https://artifacthub.io/packages/helm/floating-server/floating-server).
{% endstep %}

{% step %}

### Deploy with Helm

Ensure your Redis setup is configured on the Kubernetes cluster. After that, deploy the Floating Server with the Helm chart, specifying the correct values for your environment.
{% endstep %}

{% step %}

### Monitoring and Scaling

Set up monitoring using tools like Prometheus and Grafana to observe the server's health. Additionally, configure auto-scaling based on the number of active licenses to ensure optimal performance.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Prerequisite: Redis must be configured and available in your Kubernetes cluster before deploying the Floating Server.
{% endhint %}


---

# 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://docs.licensespring.com/floating-server/floating-server-v1/deployment-methods/kubernetes-helm/installation-steps.md?ask=<question>&goal=<endgoal>
```

`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.