> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/installation/artifacts/ansible-playbooks/application-playbooks.md). # Application Playbooks Application playbooks are used to deploy all core Rierino platform components They are typically executed through [deployer](/installation/artifacts/helm-charts/initialization-charts/deployer.md) jobs or requests to the [deployer API](/installation/artifacts/helm-charts/initialization-charts/deployer-api.md) service, although they can be also triggered through command line directly. All playbook helm chart deployments have a "state" variable, which can be passed as "absent" to remove the related release from Kubernetes cluster.

Playbook	Description
Gateway Helm	Used to deploy gateway, authentication and session helm charts, loading their packages from the maven repository and configurations as deployment assets
Runner Helm	Deploys runners using configurations as deployment asset files or from rest API for a given deployment id using samza, spring, socket runner helm charts, loading their packages from the maven repository
Admin UI Helm	Deploys admin UI on Kubernetes cluster using admin ui helm chart and the specific image from docker repository
Storefront Helm	Deploys a demo storefront with given template and storefront helm chart using the specific image from docker repository
H2O Wave Helm (Deprecated)	Deploys H2O Wave gateway using h2o wave helm chart and the specific image from docker repository
Wave App Helm (Deprecated)	Loads wave app configurations from deployment asset files and deploys a wave app helm chart using the specific image from docker repository

--- # 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.rierino.com/installation/artifacts/ansible-playbooks/application-playbooks.md?ask=&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.