> 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/devops/administration/managing-deployments.md).

# Managing Deployments

Once defined, it is possible to perform the following actions on a [deployment](/devops/microservices/deployment-packages.md) through the editor menu (for more commands, [Command Center](/devops/administration/sending-commands.md) can be used):

* **Deploy:** Makes a call to "/Deploy" API endpoint with current deployment's id to trigger the CD task responsible for runner deployments.
* **Undeploy:** Makes a call to "/Undeploy" API endpoint with current deployment's id to trigger the CD task responsible for runner removals.
* **Restart:** Makes a call to "/Restart" API endpoint with current deployment's id to trigger the CD task responsible for runner restarts.
* **Deployments:** Makes a call to "/GetDeployments" API endpoint with current deployment's id to get status of current deployment on K8s.
* **Pods:** Makes a call to "/GetPods" API endpoint with current deployment's id to get a list of pods running current deployment on K8s.
* **Logs:** Makes a call to "/GetLogs" API endpoint with current deployment's id to get last log lines from the current deployment on K8s.
* **Ping:** Sends a ping command to all runners of a deployment and waits for 5 seconds to check if all are healthy.

It is possible to get the full list of K8s deployments from "Deployments" lister menu as well.

{% hint style="info" %}
Actions such as "Deploy" and "Undeploy" are executed with Rest API calls to the kubernetes cluster (e.g. kubectl) or automation tool (e.g. Jenkins) depending on the deployment platform and their status can be monitored from its own interface.
{% 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.rierino.com/devops/administration/managing-deployments.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.