Skip to content

fix: auto-fetch cloud public CIDRs without cloud sync permissions#660

Merged
RomanMelnyk113 merged 5 commits intomainfrom
well-known-cloud-cidr
Mar 18, 2026
Merged

fix: auto-fetch cloud public CIDRs without cloud sync permissions#660
RomanMelnyk113 merged 5 commits intomainfrom
well-known-cloud-cidr

Conversation

@RomanMelnyk113
Copy link
Contributor

@RomanMelnyk113 RomanMelnyk113 commented Mar 10, 2026

Previously, cloud service IP ranges (used for network flow classification) were only fetched when --cloud-provider-vpc-sync-enabled=true, which requires full cloud credentials for VPC API calls. However, the IP range fetch itself only hits public unauthenticated endpoints. This meant clusters without cloud credentials got no cloud CIDR data at all, leaving CloudCidr empty in GetClusterInfo responses and breaking downstream traffic classification.

Now, setting --cloud-provider=aws (or gcp) is sufficient - cloud public CIDRs are fetched independently, and full VPC sync remains opt-in for richer subnet/zone data.

Summary

  • Extract cloud service IP range fetching (AWS/GCP) into standalone serviceranges package - these are unauthenticated HTTP GETs to public endpoints (ip-ranges.amazonaws.com, gstatic.com/ipranges/cloud.json)
  • Add CloudPublicCIDRController that runs automatically when --cloud-provider is set, with no extra cloud credentials needed
  • Add third-tier lookup in NetworkIndex: static > cloud-sync > cloud-public (lowest priority)

@RomanMelnyk113 RomanMelnyk113 changed the title public cloud cidrs sync without need to provide any permissions feat: auto-fetch cloud public CIDRs without cloud sync permissions Mar 10, 2026
@RomanMelnyk113 RomanMelnyk113 changed the title feat: auto-fetch cloud public CIDRs without cloud sync permissions fix: auto-fetch cloud public CIDRs without cloud sync permissions Mar 11, 2026
@RomanMelnyk113 RomanMelnyk113 merged commit 0de8ebb into main Mar 18, 2026
3 checks passed
@RomanMelnyk113 RomanMelnyk113 deleted the well-known-cloud-cidr branch March 18, 2026 11:36
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.

2 participants