> 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/enabler-playbooks.md).

# Enabler Playbooks

Enabler playbooks are used to deploy applications such as database systems, file systems, messaging queues which are used by the Rierino platform.

These playbooks are optional, since it is possible to use existing deployments or deploy such applications using cloud vendor marketplaces or SaaS providers. Their primary purpose is to enable automation of cloud agnostic deployments.

Not all these deployments are mandatory, as many of them are used for specific types of modules only. 

<table><thead><tr><th width="188.33333333333331">Playbook</th><th>Description</th><th>Requirement</th></tr></thead><tbody><tr><td>MongoDB</td><td>Install, uninstall and service stop/restart playbooks for managing a distributed, non-containerized MongoDB deployment</td><td>Typically used, but can be replaced with a different DBMS</td></tr><tr><td>Keycloak</td><td>Install, uninstall playbooks for a high availability, non-containerized deployment of Keycloak instances with Postgres persistence</td><td>Typically used, but can be replaced with a different authentication provider</td></tr><tr><td>Kafka</td><td>Install, uninstall playbooks for Strimzi based Kubernetes deployment of a Kafka cluster</td><td>Not required unless Kafka based runners are utilized</td></tr><tr><td>Elasticsearch</td><td>Install, uninstall playbooks for a distributed, non-containerized Elasticsearch cluster deployment</td><td>Not required unless search query managers are utilized</td></tr><tr><td>Redis</td><td>Install, uninstall playbooks for a high availability, non-containerized deployment of Redis Sentinel</td><td>Not required unless shared cache states are utilized</td></tr><tr><td>Consul</td><td>Install, uninstall playbooks for a distributed, non-containerized Consul service discovery deployment</td><td>Not required if Kubernetes services are utilized for discovery</td></tr><tr><td>Etcd</td><td>Install, uninstall playbooks for a distributed, non-containerized etcd cluster deployment</td><td>Not required if Kubernetes config maps are utilized for KV loading</td></tr><tr><td>Vault</td><td>Install, uninstall playbooks for a distributed, non-containerized HashiCorp Vault cluster deployment</td><td>Not required if Kubernetes secrets are utilized for secret loading</td></tr><tr><td>Airflow</td><td>Install, uninstall playbooks for deployment of Kubernetes based Airflow services</td><td>Not required unless scheduled services are utilized</td></tr><tr><td>NiFi</td><td>Install, uninstall playbooks for a distributed, non-containerized NiFi cluster deployment</td><td>Not required unless big data flows are utilized (typically deployed together with Hadoop, Hive, Presto and Druid)</td></tr><tr><td>Nexus</td><td>Install, uninstall playbooks for a distributed, non-containerized Nexus cluster deployment</td><td>Not required if GitHub packages are utilized</td></tr><tr><td>Jenkins</td><td>Install, uninstall playbooks for a distributed, non-containerized Jenkins cluster deployment</td><td>Not required if GitHub actions are utilized</td></tr></tbody></table>


---

# 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/enabler-playbooks.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.