Skip to content

geoip: support additional maxmind database fields#46074

Open
tufitko wants to merge 1 commit into
envoyproxy:mainfrom
tufitko:geoip-maxmind-extended-fields
Open

geoip: support additional maxmind database fields#46074
tufitko wants to merge 1 commit into
envoyproxy:mainfrom
tufitko:geoip-maxmind-extended-fields

Conversation

@tufitko

@tufitko tufitko commented Jul 10, 2026

Copy link
Copy Markdown

Commit Message: geoip: support additional maxmind database fields
Additional Description:

Adds new geolocation field keys to the common geoip provider config and their extraction in the maxmind provider: city_geoname_id, latitude, longitude, time_zone, postal_code, region_name, region_geoname_id, subregion_geoname_id, country_geoname_id, continent_geoname_id and metro_code. 
Country-level GeoNames IDs follow the existing country ISO code semantics: the country database is preferred with a fallback to the city database. Adds UINT16 (metro code) and DOUBLE (latitude/longitude) entry data type support to the lookup result population.

Motivation: parity with the nginx geoip2 module headers when migrating ingress from nginx to Envoy.

Risk Level: low?
Testing: tests addded
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

Adds new geolocation field keys to the common geoip provider config and
their extraction in the maxmind provider: city_geoname_id, latitude,
longitude, time_zone, postal_code, region_name, region_geoname_id,
subregion_geoname_id, country_geoname_id, continent_geoname_id and
metro_code. Country-level GeoNames IDs follow the existing country ISO
code semantics: the country database is preferred with a fallback to the
city database. Adds UINT16 (metro code) and DOUBLE (latitude/longitude)
entry data type support to the lookup result population.

Motivation: parity with the nginx geoip2 module headers when migrating
ingress from nginx to Envoy.

Signed-off-by: Andrei Vydrin <andrey.vydrin@jetradar.com>
@tufitko tufitko requested a deployment to external-contributors July 10, 2026 07:58 — with GitHub Actions Waiting
@repokitteh-read-only

Copy link
Copy Markdown

Hi @tufitko, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #46074 was opened by tufitko.

see: more, trace.

@repokitteh-read-only

Copy link
Copy Markdown

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #46074 was opened by tufitko.

see: more, trace.

@tufitko tufitko marked this pull request as ready for review July 10, 2026 08:23
@repokitteh-read-only

Copy link
Copy Markdown

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to (api/envoy/|docs/root/api-docs/).
envoyproxy/api-shepherds assignee is @markdroth
CC @envoyproxy/api-watchers: FYI only for changes made to (api/envoy/|docs/root/api-docs/).

🐱

Caused by: #46074 was ready_for_review by tufitko.

see: more, trace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants