Skip to content

Add NGINX ingress rate limiting to protect against traffic spikes - #843

Merged
rdimitrov merged 2 commits into
mainfrom
add-rate-limitting
Dec 12, 2025
Merged

rdimitrov merged 2 commits into
mainfrom
add-rate-limitting

Conversation

@rdimitrov

Copy link
Copy Markdown
Member

Motivation and Context

The following is an alternative solution to #833

Goal is to deploy and promote it to prod, then monitor the alerts for a week to see its effect and reassess. In case it's actual traffic that we've started blocking we can also up the replicas. I thought it doesn't make sense to up them now since it would be nice to isolate the result of this change first.

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@rdimitrov
rdimitrov requested a review from a team December 12, 2025 08:42
Comment thread deploy/pkg/k8s/registry.go Resolved
@rdimitrov
rdimitrov requested a review from toby December 12, 2025 21:53
@rdimitrov
rdimitrov merged commit 19c58c1 into main Dec 12, 2025
5 checks passed
@rdimitrov
rdimitrov deleted the add-rate-limitting branch December 12, 2025 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants