> For the complete documentation index, see [llms.txt](https://docs.feast.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feast.dev/v0.21-branch/how-to-guides/fetching-java-features-k8s.md).

# Deploying a Java feature server on Kubernetes

This tutorial guides you on how to:

* Define features and data sources in Feast using the Feast CLI
* Materialize features to a Redis cluster deployed on Kubernetes.
* Deploy a Feast Java feature server into a Kubernetes cluster using the Feast helm charts
* Retrieve features using the gRPC API exposed by the Feast Java server

Try it and let us know what you think!

| ![](https://3677529471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVkSG27xI2Nd7tq6rJzMY%2Fuploads%2Fgit-blob-8b25551a97921681334176ee143b41510a117d86%2Fgithub-mark-32px.png?alt=media)[ View guide in Github](https://github.com/feast-dev/feast/blob/v0.21-branch/examples/java-demo/README.md) |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |


---

# 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.feast.dev/v0.21-branch/how-to-guides/fetching-java-features-k8s.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.