Skip to content

Commit 052bec6

Browse files
Update articles/operator-nexus/reference-nexus-kubernetes-cluster-sku.md
Co-authored-by: Dinesh Kumar Ramasamy <[email protected]>
1 parent 98e59c7 commit 052bec6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/operator-nexus/reference-nexus-kubernetes-cluster-sku.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ All these SKUs are having the following characteristics:
2929
The general purpose and performance optimized VM SKUs can be used for both worker and control plane nodes within the Azure Operator Nexus Kubernetes cluster. Memory optimized VM SKUs can only be used for worker nodes.
3030

3131
> [!NOTE]
32-
> To use these VM SKUs, hardware compatibility should be considered. Operator Nexus offers two hardware options: BOM 1.7.3 and BOM 2.0 (More details [here](./reference-operator-nexus-skus.md)). The larger VM SKUs, specifically `NC_G56_224_v1`, `NC_P54_224_v1`, and `NC_E110_448_v1`, can only be supported on hardware BOM 2.0.
32+
> To use these VM SKUs, hardware compatibility should be considered. Operator Nexus offers two hardware options: BOM 1.7.3 and BOM 2.0 (More details [here](./reference-operator-nexus-skus.md#compute-skus)). The larger VM SKUs, specifically `NC_G56_224_v1`, `NC_P54_224_v1`, and `NC_E110_448_v1`, can only be supported on hardware BOM 2.0.
3333
>
3434
> Nexus Tenant Kubernetes cluster VM SKUs are compatible with BOM 2.0, enabling users to use them alongside the larger SKUs. However, if a user tries to use BOM 2.0-specific SKUs on BOM 1.7.3 hardware, they will encounter an "insufficient resources" error during resource creation.
3535

0 commit comments

Comments
 (0)