Scale-out is needed prior to NAPP Upgrade to 4.2.0

Products

• VMware vDefend Firewall
• VMware vDefend Firewall with Advanced Threat Prevention

Issue/Introduction

In NAPP version 4.2.0, the minimum worker node requirement has been increased: 
- NAPP Platform + Intelligence - from 3 in earlier version increase to 4 nodes
- NAPP Platform + Intelligence +NDR + MPS - from 3 in earlier version increase to 5 nodes

If you have NAPP deployed with a version earlier than 4.2.0 and the worker node count is 3, the upgrade pre-check will attempt to identify resource constraints and prompt for a scale-out if additional nodes are needed.

Sample pre-check error message: "Kubernetes cluster does not have enough resources to upgrade Metrics. Required CPU-Memory: [44317m, 199153MB], Available CPU-Memory: [48000m, 192923MB]".

In this case, the user is expected to scale out the worker nodes to resolve the error.

Environment

NAPP 4.2.0

Resolution

Before starting the upgrade, in the existing Kubernetes cluster, please take action to:
- increase the worker nodes from 3 to 4 (for NAPP Platform + Intelligence deployment) ,
- or increase the worker nodes from 3 to 5 (for NAPP Platform + Intelligence +NDR + MPS deployment)

For customers who already had additional worker nodes added prior to upgrade because they saw high memory alarms and subsequently added nodes with GSS help - They might not require an extra node. It all depends on how many features were installed and how many nodes were added. The upgrade pre-check will do best-effort to alert them pre upgrade if extra nodes are required or not. 

For steps to increase worker nodes in TKC, please refer to the following documentation:
VMware vSphere with Tanzu - Scaling Worker Nodes : https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-29DA638D-23B5-4A53-9152-7BD5D5F85BFE.html