feat: add taint & toleration to mainnet3 relayer node pool (#4780)
### Description See https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/ - In GKE, for the larger relayer node pool, added a taint: `NoSchedule`, label `component=relayer` - In our relayer workloads, they now have a toleration that matches that taint - As part of rollout, first did a NoExecute (evicting everything on the big nodes), then moved to NoSchedule (so that some other pods like daemonsets would still get onto these bigger nodes). I made sure the hyperlane and neutron context relayers have these tolerations ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Fixes https://github.com/hyperlane-xyz/issues/issues/1309 ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->pull/4789/head
parent
83a1567a0a
commit
fc3818d12a
Loading…
Reference in new issue