Namespace—Namespace in the existing Kubernetes cluster where the CN-Series HSF will be deployed.

Node Info— Node pool labels are used to deploy each type of CN pod. You need to specify the CPU, Memory and Desired Pods for each of the pod types based on the availability on the nodes. The Labels and the Label value pairs are prerequisite values to exist on the node and you have to add the same key value pair used to label the nodes.

Interfaces—Interface names for CN-DB, NGFW, CN-GW pods need to be added. Each Interface requires specific net-attach-def to be applied on the Kubernetes cluster. The plugin will name Ethernet x/1 and Ethernet x/2 by default. If you change the interface names for Ethernet x/1 and Ethernet x/2, then you will need to make the change in the network attachments section also. For the CN-GW pod, you can add up to 12 interfaces excluding CI and TI interfaces.

CN-Series Cluster Name—Name for the CN Series HSF.

Image—You need to store the images either in the local or AWS repository and this cannot be validated by Panorama. However, Kubernetes cluster has connectivity to the repositories where the images are stored.

1. CN-MGMT Image: The complete URI from the repository where the image is to be accessed by the Kubernetes environment for deploying the CN-MGMT pod.
2. CN-MGMT INIT Image: The init image needed for CN- MGMT pod.
3. CN-NGFW Image: The complete URI from the repository where the image is to be accessed by the Kubernetes environment for deploying CN-NGFW pod.

Storage—If you would like to configure exclusive storage, click Dynamic in the Storage section for EKS environment and Static or Dynamic for Openshift environments and the plugin will configure the cloud storage. If you have chosen Static then you need to enter the Storage Key Values, Worker Nodelabel Key and Worker Nodelabel Value. You also need to enter the Path where the storage is mounted.

Certificates—This is the Device certificate information to Enable or Disable information such as licensing and if enabled, you will need to provide the PIN ID and PIN VALUE.

Primary Panorama IP—Displays values of the public and private IP addresses of the Panorama on which the plugin is installed.

Secondary Panorama IP—Displays values of the public and private IP addresses of the secondary Panorama (in case of HA) on which the plugin is installed.

Device Group—You need to create a DG before configuring the deployment as mentioned in the prerequisite section. The Device Group dropdown lists all the DGs on the current Panorama and you need to choose a valid DG. The CN-MGMT pod will be registered under this DG. For steps to create a Device Group, see Step 5 of Prepare Panorama for CN-Series HSF Deployment.

Template—You need to create a template (variable_template) for CN-GW specific details, before configuring the deployment as mentioned in the prerequisite section. The Template drop-down lists all the templates on the current Panorama. You need to choose a template suitable for your current deployment. After HSF deployment, this template will be added to a template stack by the plugin along with a K8S-CNF-Clustering-Readonly template which handles the basic configuration for CN-DB and CN-NGFW pods. It also configures the CI and TI links on the CN-GW pod. The CN-MGMT pod gets configurations from the template stack. For steps to create the variable template, see Step 6 of Prepare Panorama for CN-Series HSF Deployment.

Log Collector Group (LCG)—This drop-down lists all the Log Collector Groups on the current Panorama and a suitable LCG needs to be chosen. It also configures the CI and TI links of the CN-GW pod. For steps to create LCG, see Step 7 of Prepare Panorama for CN-Series HSF Deployment.

Jumbo Frame—The Jumbo Frame dropdown lists values - Enable, Disable, and AutoDetect. This configuration is applicable for all the pods in the CN-Series HSF.

5G Enabled—This is a radio button with Enable and Disable options and refers to the GTP configuration needed on the CN-Series HSF.

DPDK—This is a radio button with Enable and Disable options. If the underlying resources do not support DPDK, then by default the CN-Series HSF will be defaulted to packetmmap.

CPU Pinning—Choose to Enable or Disable CPU Pinning.

Numa Enabled—Provide the Node number for NUMA.

CPU Pinning Base—Provide the CPU number from where you wish to start cpu pinning of forwarding processes and skip the lower numbered CPUs.

Enter the Autoscaling Metric, Scale In Threshold and Scale Out Threshold in the Autoscaling section.

Click OK to commit the deployment.