> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/kubernetes-overview/pod-toleration.md).

# Pod Toleration

Support for specifying Kubernetes YAML for Pod Toleration

DuploCloud supports the customization of many Kubernetes (K8s) YAML operators, such as [`tolerations`](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/). If you are using a Docker container, you can specify the `tolerations` operator configuration in the **Other Container Config** field in the container definition in DuploCloud

## Specifying Pod Toleration

1. In the DuploCloud Portal, navigate to **Kubernetes** -> **Services**. The **Services** page displays.
2. Select the **Service** from the **NAME** column.
3. From the **Actions** menu, select **Edit**. The **Edit Service** page displays.<br>

   <figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FfDxl459pM3fMDHEo50W3%2Ftol1.png?alt=media&amp;token=99c8c80a-e02c-4033-8375-8adf6b9f3dda" alt=""><figcaption><p><strong>Edit</strong> option in <strong>Actions</strong> menu on <strong>Edit Service</strong> page</p></figcaption></figure>
4. Click **Next** to proceed to the **Advanced Options** page.
5. In the **Other Container Config** field, add the `tolerations` operator YAML you have customized for your container.<br>

   <div align="left"><figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fb1JddyMNYhfkRpYtGLyS%2Ftol2.png?alt=media&amp;token=272cb1f7-d537-428c-8bdd-481b9f4722f9" alt=""><figcaption><p><strong>Other Container Config</strong> field in <strong>Advanced Options</strong> page</p></figcaption></figure></div>
6. Click **Update**. Your container has been updated with your custom specifications for the `tolerations` operator.

### Example Code: `tolerations` operator YAML

In this example:

* If a Pod is running and a taint matching `key1` exists on the node, then the Pod will not schedule the node (`NoSchedule`).
* If a Pod is running and a taint matching `example-key` exists on the node, then the Pod stays bound to the node for `6000` seconds and then is evicted (`NoExecute`). If the taint is removed before that time, the Pod will not be evicted.

{% code title="tolerations YAML" %}

```yaml
tolerations:
  - key: key1
    operator: Equal
    value: value1
    effect: NoSchedule
  - key: example-key
    operator: Exists
    effect: NoExecute
    tolerationSeconds: 6000
```

{% endcode %}


---

# 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.duplocloud.com/docs/automation-platform/kubernetes-overview/pod-toleration.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.
