SolvedAPI & Developers
Getting 429 from the check-in endpoint in our Kubernetes cluster
We moved our cron jobs into Kubernetes and now some heartbeat check-ins fail with 429. Each job pings its own heartbeat and none of them run more than once a minute individually, so I do not understand why we are being rate limited.
Answered by Elif Kaya, MonoDuty Support Engineer9 days ago77 found this helpful