Skip to content

Update NFC deployment requirements and recommendations #3875

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update NFC deployment requirements and recommendations #3875

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion operator-nexus/howto-configure-network-fabric-controller.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,14 @@ With the latest update, all new NFC Cluster deployments uses `Standard_D8s_v3` v
This change is required due to the limited availability of `Standard_Ds4_v2` in several Azure regions.

> [!Note]
> Existing NFC Clusters will continue to run on `Standard_Ds4_v2.
> To ensure optimal performance and scalability, it is essential to provision the appropriate node pool count for the required number of Network Fabric instances (NFs) within each Network Fabric Controller (NFC). If the necessary node pool count is not available, a provisioning request must be submitted in advance. Based on the current configuration—**recommended SKU: StandardDS4v2 (8 vCPUs, 28 GiB Memory)**—the expected node pool scaling requirements for the AKS cluster named nfcCluster are as follows: <br>
>
>| Number of NFs per NFC | Minimum Node Pool Count Required in AKS Cluster nfc Cluster|
>|---------------------- |------------------------------------------------------------|
>|1 – 5 | 2 |
>|6 - 10 | 3 |
>|11 - 15 | 4 |


### Minimum vCPU requirement

Expand Down