Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider blocking some invalid requests at the edge #275

Open
BenTheElder opened this issue Feb 14, 2024 · 0 comments
Open

Consider blocking some invalid requests at the edge #275

BenTheElder opened this issue Feb 14, 2024 · 0 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@BenTheElder
Copy link
Member

I bet it costs less to apply security policies in app armor than to serve through to the registry, and we get a crapload of invalid requests to endpoints like /v2/_catalog that we could probably 404 at the load balancer before it even hits cloud run?

We should double check the feasibility and pricing of blocking some of these common bad requests at the LB (spot checking I think this checks out).

This would be implemented in the terraform in k8s.io, but tracking here.

As the cloud run is only around 2k/month right now so no rush, just an idea for the back burner.

/priority backlog
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

2 participants