Update ip ranges for Q1 2025

[upodroid]

It has been a while since we updated the IP ranges #288

[dims]

aws-ip-ranges.json is impossible to review! 🙃

/approve
/lgtm

/hold until we need to merge!

[BenTheElder]

aws-ip-ranges.json is impossible to review! 🙃

you could diff it versus the upstream source, we could try to enforce that but it's difficult because we don't want CI to break everytime there's new data.

I primarily look to see that it looks like valid data, the actual values at worst would just make us less efficient if they're wrong (e.g. if there was a block covering the entire IP space to one vendor)

The generated code file I believe we already lint verify, but otherwise we just want to look for malicious init type behavior right?

[BenTheElder]

/lgtm
/approve

[BenTheElder]

At some point we might consider further optimizing the data load and lookup but ... so far it's YAGNI. Last I checked the request logs cost more than the cloud run compute and our responses are pretty fast.

[upodroid]

I'll cancel the hold after I verify #300 works

[xmudrii]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, dims, upodroid, xmudrii

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [BenTheElder,dims]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[upodroid]

/hold cancel

autodeploy works