# Operator Tolerations

**URL:** <https://forum.ansible.com/t/operator-tolerations/3819>\
**Category:** Get Help\
**Tags:** awx\
**Created:** [February 12, 2024, 10:25am UTC](https://forum.ansible.com/t/operator-tolerations/3819 "2024-02-12T10:25:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JonTheNiceGuy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jontheniceguy/32/2267_2.png) [@JonTheNiceGuy](https://forum.ansible.com/u/JonTheNiceGuy)\
**Post date:** [February 12, 2024, 10:25am UTC](https://forum.ansible.com/t/operator-tolerations/3819/1 "2024-02-12T10:25:48Z")

</div>

Hi, I’m trying to deploy the AWX-Operator on an EKS cluster where the nodes are all configured with Taints.

I can see how to influence the final deployed resources that the operator creates, but I can’t see if there’s any way with helm to change the behaviour of the operator deployment.

I suspect that I need to add the toleration between these two lines here: [awx-operator/config/default/manager\_config\_patch.yaml at devel · ansible/awx-operator · GitHub](https://github.com/ansible/awx-operator/blob/devel/config/default/manager_config_patch.yaml#L10-L11)

However, as I’m currently consuming the helm chart - I don’t exactly know how that will trickle down into the values.yaml. It looks like to make any meaningful changes, I’d need to move `config/manager/manager.yaml` into `.helm/starter/templates` but that feels like a big move! Any thoughts before I raise an issue to address this?

Or, alternatively, am I better off just taking the basic install instructions ([Basic install - Ansible AWX Operator Documentation](https://ansible.readthedocs.io/projects/awx-operator/en/stable/installation/basic-install.html)) and tweaking the files before they deploy?

I’d like to make this a mostly-automated install, if I can! I don’t really want to be telling people to manually edit files to do the deployment.

---

<div class="post-metadata">

**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\
**Post date:** [February 12, 2024, 2:21pm UTC](https://forum.ansible.com/t/operator-tolerations/3819/2 "2024-02-12T14:21:55Z")

</div>

Hi, the `kustomization.yaml` way in the basic install is handy way to customize operator deployment.

You can add `patches` in the `kustomization.yaml` (See the last three lines)

```yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
  # Find the latest tag here: https://github.com/ansible/awx-operator/releases
resources:
- github.com/ansible/awx-operator/config/default?ref=2.11.0

# Set the image tags to match the git version from above
images:
- name: quay.io/ansible/awx-operator
  newTag: 2.11.0

# Specify a custom namespace in which to install AWX
namespace: awx

# Apply patch to specific deployment ✅
patches: ✅
  - path: manager_patch.yaml ✅

```

And here is the `manager_patch.yaml`

```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: controller-manager
  namespace: system
spec:
  template:
    spec:
      tolerations:
        - key: "key1"
          operator: "Equal"
          value: "value1"
          effect: "NoSchedule"

```

This allows for customization of operator deployment in a declarative manner.

Refer to the official kustomize docs for further information: [patches | SIG CLI](https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/patches/)

Hope this helps 😃