[Epic] 3.5: Kubernetify RPC nodes

[mfw78]

Epic label: E:3.5 Kubernetify RPC nodes
Planned start date: 20/02/2024
Due date: 11/03/2024

Summary

As Dencun approaches, we are being forced to upgrade our RPC nodes, and this gives us the opportunity to simultaneously eliminate a raft of tech debt. This Epic facilitates the movement of all RPC nodes from the legacy AWS account to internal services running within respective Kubernetes clusters.

Acceptance Criteria

• RPC nodes in kubernetes
• Comprehensive metrics monitoring of RPC nodes
• Zero-downtime (HTTP JSON-RPC only, not including websockets) node upgrade methodology
• SLA to be able to deploy new nodes, fully synced, within 6 hrs
• A/B methodology (production and staging environments to be identical)

Tasks

• cowprotocol/infrastructure#1124
• cowprotocol/infrastructure#1125
• cowprotocol/infrastructure#1127
• cowprotocol/infrastructure#1158
• cowprotocol/infrastructure#1159
• cowprotocol/infrastructure#1153
• cowprotocol/infrastructure#1154
• cowprotocol/infrastructure#1155
• cowprotocol/infrastructure#1152
• cowprotocol/infrastructure#1202
• cowprotocol/infrastructure#1199
• cowprotocol/infrastructure#1203
• cowprotocol/infrastructure#1208
• cowprotocol/infrastructure#1204
• cowprotocol/infrastructure#1156
• cowprotocol/infrastructure#1207
• cowprotocol/infrastructure#1380