extended maxCount of MC userAgentPool

[mukrishn]

To support swiftv2 networking for ARO-HCP

What

Extend maxCount of userAgentPool to 15 per region, so it can scale up to 45 nodes for HCP.

Why

• With Swift networking in ARO-HCP, each node is limited to a maximum of 7 NICs, which effectively limits it to hosting up to 7 router pods per node.
• Each HCP deploys 3 router replicas, so 100 HCPs result in 300 router pods.
• With a placement limit of 7 router pods per node, this requires approximately 300 / 7 ≈ 43 nodes.
• Therefore, we need more than 14 replicas per region in the userAgentPool to accommodate the router pod distribution safely.

cc: @geoberle @stevekuznetsov

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mukrishn
Once this PR has been reviewed and has the lgtm label, please assign ashishmax31 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• config/OWNERS

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

[Copilot]

Pull request overview

This PR increases the AKS userAgentPool.maxCount limit to support scaling management clusters for Swift V2 networking, enabling higher router pod density across more nodes as HCP count grows.

Changes:

• Bumped userAgentPool.maxCount from 14 → 15 in three management-cluster configuration blocks (per-region capacity increase).

[openshift-ci]

@mukrishn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-parallel	be39b05	link	true	/test e2e-parallel

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[stevekuznetsov]

We would be overcomitting on CPU & mem if we do this, though, won't we?