> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/operations/deployment/deployment-guide/rerun-jobs-in-kubernetes-cluster.md). # Rerun Jobs in Kubernetes Cluster This guide provides instructions on how to rerun jobs in Kubernetes cluster. In Kubernetes, Jobs are used to rerun tasks that are expected to terminate or end. Sometimes, it may be necessary to rerun a job, either because it failed or because you need to run the task again. Below are the steps to rerun jobs in a Kubernetes cluster. ## **Prerequisites** * You need `kubectl` installed and configured to access your Kubernetes cluster. * Ensure you have the necessary permissions to manage jobs in your cluster. ## Procedure 1. Determine the name of the job you want to rerun. You can list the jobs in a namespace. ```bash kubectl get jobs -n ``` 2. Delete the current job to rerun a job. This will also delete the associated pods. ```bash kubectl delete job -n ``` 3. After deleting the current job, you need to recreate it. You can use the same YAML file or command that was used to create the job initially. ```sh kubectl apply -f .yaml -n ``` 4. After recreating the job, you should verify that the job has been recreated and is running as expected. ```bash kubectl get jobs -n ``` 5. You can monitor the logs of the job's pod to ensure that it is running correctly and completing the task. ```sh kubectl logs -f job/ -n ``` --- # 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.openg2p.org/operations/deployment/deployment-guide/rerun-jobs-in-kubernetes-cluster.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.