Deployments allow grouping of runners into physical components, as well as configurations for deploying same runners on different infrastructure (e.g. different cloud providers, different containerization models) based on business and technical requirements.
In the most typical scenario, a deployment package bundles a few runners, specifies kubernetes deployment parameters such as namespace, node pool, rierino version and replica count, which results in deployment of a Java application using Rierino's in-cluster deployer web service and kubernetes job running ansible playbooks and helm charts. However, it is possible to 100% customize this deployment model, since the deployment activity is basically a Rierino backend API call with the deployment package ID, which can easily trigger a Jenkins job for an on-prem deployment, etc. It is even possible to use deployment packages for non-runner deployments (e.g. ui, gateway, etc.) with minimal customizations on the deployment API design.
---
# Agent Instructions: 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:
```
GET https://docs.rierino.com/devops/microservices/deployment-packages.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.