Feature: Make vpc.max.networks dynamic and improve the limit-reached error #14372

Activity

1. MitchDrage

   changed the title [-]Allow per-Domain/Account VPC tier limits[/-] [+]Feature: Allow per-Domain/Account VPC tier limits[/+] on Oct 9, 2026
2. github-actions

   added

   component:networking

   component:vpc

   type:new-feature

   on Oct 9, 2026
3. github-actions commented on Oct 9, 2026

   

   github-actionsbot

   on Oct 9, 2026 – with GitHub Actions

   More actions

   🎯 Triage report

   This is a feature request to make the per-VPC tier (network) limit configurable at the domain/account level instead of only as the global setting vpc.max.networks, and to improve the generic/uninformative API error returned when the limit is hit.

   📊 Assessment

   Dimension	Value	Reasoning
   Type	type:new-feature	Requests new configurability (per-domain/account limit) plus an improved error message, not a fix to existing broken behavior.
   Component	component:vpc, component:networking	Directly relates to VPC tier/network creation limits (VpcManagerImpl, vpc.max.networks).
   Severity	n/a	Not a bug, so severity does not apply.
   Labels	type:new-feature, component:vpc, component:networking	See above.
   Coding agent	Needs more info	The error-message improvement (propagate CloudRuntimeException message instead of generic "Internal error executing command") is fairly self-contained and could be tackled by an agent. However, making the VPC tier limit per-domain/account configurable is a larger design change (new setting scope, API params, UI, docs) requiring maintainer/architecture input before implementation.

   🔗 Similar issues

   No similar open issues were found in a search for related terms (vpc.max.networks, VPC tier limit).

   💡 Notes and suggestions

   • Two distinct asks are bundled here; maintainers may want to split them:
     1. Configurability: Promote vpc.max.networks from a global-only setting to one overridable per domain/account, similar to how VPC count limits already work (max.account.vpcs style per-domain/account overrides).
     2. Error UX: The API currently surfaces a generic Request failed (530): Internal error executing command to the caller while the real cause (CloudRuntimeException: Number of networks per VPC cannot surpass [3]) is only visible in management server logs. This should be a quick win — propagate the specific exception message to the API response, similar to other resource-limit checks in VpcManagerImpl.
   • Relevant code: VpcManagerImpl (network/tier creation path) and the vpc.max.networks global config definition.
   • Suggest confirming with the reporter whether they need both items or primarily the error-message fix, which is lower risk and could be a good first contribution.

   Generated by Daily Issue Triage · sonnet50 71.3K · ◷

   Add this agentic workflows to your repo

   To install this agentic workflow, run

   gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9
   
4. MitchDrage

   changed the title [-]Feature: Allow per-Domain/Account VPC tier limits[/-] [+]Feature: Make vpc.max.networks dynamic and improve the limit-reached error[/+] on Oct 10, 2026
5. MitchDrage commented on Oct 10, 2026

   

   MitchDrage

   on Oct 10, 2026

   Author

   More actions

   I've changed the scope of this issue. Per-account/domain values aren't needed: the cap exists to handle the VR's NIC capacity which is the same for every tenant, and VPC tiers already count toward the account and domain guest network limits. This now covers making the setting dynamic and improving the error. See #14373.