Install the Kubernetes Plugin and Set up Panorama for CN-Series
Install the Kubernetes plugin on Panorama and set it up to monitor your Kubernetes clusters.
You can deploy the Panorama appliance on-premises or in the cloud, as long as the Panorama appliance can connect with the Kubernetes clusters where you want to deploy the CN-Series firewalls. This workflow takes you through the process of installing the Kubernetes plugin, activating the auth code and setting up the Kubernetes plugin to monitor your clusters.
You must carefully plan the number of credits you want to allocate to Panorama. After changing the number of credits, you need not redeploy the CN-Series firewall on Panorama OS 10.1.
For more information, see License the CN-Series Firewall and Software NGFW Credit Estimator.
- Deploy a Panorama with software version 10.1 and install the minimum content version.
- Go to) for the minimum content release version on PAN-OS 10.1.PanoramaDynamic Updates
- Go tofor the software version.PanoramaSoftwareLocate and download the model-specific file for the release version to which you are upgrading. For example, to upgrade an M-Series appliance to Panorama 10.1.0, download the Panorama_m-10.1.0 image; to upgrade a Panorama virtual appliance to Panorama 10.1.0, download the Panorama_pc-10.1.0 image.After a successful download, theActioncolumn changes from Download to Install for the downloaded image.
- Verify that your Panorama is in Panorama mode, if you want Panorama to collect the firewall logs.
- Install the Kubernetes plugin on Panorama. If your Panorama appliances are deployed as an HA pair, you must install the Kubernetes plugin on the primary (active) peer first.
- Log in to the Panorama Web Interface, selectand clickPanoramaPluginsCheck Nowto get the list of available plugins.
- SelectDownloadandInstallthe Kubernetes pluginAfter you successfully install, Panorama refreshes and the Kubernetes plugin displays on thePanoramatab.If Panorama is deployed in an HA pair, install the Kubernetes plugin on the secondary (passive) Panorama following the above steps described in Step 3.You can also verify the General Information widget on the PanoramaDashboard.
- Commit your changes on Panorama.ClickCommit to Panorama. The commit creates two templates—K8S-Network-SetupandK8S-Network-Setup-V2. It can take up to one minute for the interfaces to display on Panorama.If you have installed Kubernetes 2.0.2 plugin on CN-Series 10.1.9, the commit creates three templates—K8S-Network-Setup, K8S-Network-Setup-V1-125,andK8S Network-Setup-V2.
- K8S-Network-Setupis for use with the CN-Series as a DaemonSet and has 30 virtual wires; a pair of interfaces that are part of a virtual wire to secure an application. Therefore, the CN-NGFW as a DaemonSet can secure a maximum of 30 application pods on a node.
- K8S-Network-Setup-V1-125is for use with the CN-Series as a DaemonSet and has 125 virtual wires; a pair of interfaces that are part of a virtual wire to secure an application. Therefore, the CN NGFW as a DaemonSet can secure a maximum of 125 application pods on a node.When upgrading to CN-Series 10.1.9 version, you should use theK8S-Network-Setup-V1-125template with 250 interfaces to have 125 application pod support.K8S-Network-Setup-V1-125template on Panorama appears only after installing the Kubernetes 2.0.2 plugin on CN-Series 10.1.9.After the upgrade, on Panorama undertemplate-stack,you should replace the template withK8S-Network-Setup-V1-125template, commit and push to CN. If not replaced, only the 30 secure pods will move to the Ready State and the remaining pods fail to send the traffic.
- K8S-Network-Setup-V2is for use with the CN-Series as a Kubernetes Service and has one virtual wire; a pair of interfaces that are part of the virtual wire to secure an application.
- Get the CN-Series license credits on Panorama.
- SelectActivate/update using authorization code, and enter the auth code and the total number of dataplane vCPUs needed. You must Create a CN-Series Deployment Profile to obtain your CN-Series authcode.If you deploy the CN-Series firewall without activating the license, you have a 4-hour grace period after which the firewalls stop processing traffic. After the grace period, the CN-NGFW instances will either failopen (default) or failclosed based on the (FAILOVER_MODE) defined in thepan-cn-ngfw-configmap.yaml.In fail-open mode the firewall will receive the packets and send it out without applying any security policies. Transitioning to fail-open will require a restart and cause a brief disruption of traffic during that (expected around 10-30 seconds). In fail-closed mode, the firewall will drop all the packets it receives. A fail-close will bring down the CN-NGFW Pod and release the credits to the available credits pool for licensing new CN-NGFW Pods.
- Verify that the number of available license credits is updated.
- Generate a VM Auth Key.
- Ensure the following prerequisites are met:
- You have a computer with network access to Panorama.
- You know the Panorama IP address.
- The Management interface supports SSH, which is the default setting. If an administrator disabled SSH and you want to re-enable it: select, clickPanoramaSetupInterfacesManagement, selectSSH, clickOK, select, andCommitCommit to PanoramaCommityour changes to the Panorama configuration.
- To access the CLI using SSH:
- Enter the Panorama IP address in the SSH client and use port 22.
- Enter your administrative access credentials when prompted. After you log in, the message of the day displays, followed by the CLI prompt in Operational mode. For example:admin@ABC_Sydney>
- Use the following operational command:request bootstrap vm-auth-key generate lifetime <1-8760>For example to generate a key that is valid for 24 hrs, enter the following:request bootstrap vm-auth-key generate lifetime 24VM auth key 755036225328715 generated. Expires at: 2020/01/29 12:03:52
- You should ensure that you save the VM auth key somewhere as it is required for the later step.
- Create a parent Device Group and Template Stack.You must create a template stack and a device group, and you will later reference this template stack and device group when you edit the YAML file to deploy the CN-MGMT Pods. The Kubernetes plugin on Panorama creates a template called K8S-Network-Setup, and this template will be part of the template stack you define here.
- Create a template stack and add the K8S-Network-Setup template to the template stack.
- SelectandPanoramaTemplatesAdd Stack.
- Enter a uniqueNameto identify the stack.
- Add and select theK8S-Network-Setuptemplate for daemonset orK8S-Network-Setup-V2for kubernetes as a service deployment.
- Create a device group.
- Selectand clickPanoramaDevice GroupsAdd.
- Enter a uniqueNameand aDescriptionto identify the device group.
- Select theParent Device Group(default isShared) that will be just above the device group you are creating in the device group hierarchy.
- If you are using a Panorama virtual appliance, you can create a Log Collector and add it to a Log Collector Group.
- SelectandPanoramaCollector GroupsAdda Collector Group.
- Enter aNamefor the Collector Group.
- Enter theMinimum Retention Periodin days (1 to 2,000) for which the Collector Group will retain firewall logs.By default, the field is blank, which means the Collector Group retains logs indefinitely.
- AddLog Collectors (1 to 16) to the Collector Group Members list.
- Selectand thenCommitCommit and PushCommit and Pushyour changes to Panorama and the Collector Group you configured.
- Set up the Kubernetes plugin for monitoring the clusters.The next step in the process is to add Kubernetes cluster information to Panorama to ensure that the two can communicate with each other.Panorama supports up to 32 Kubernetes clusters.To ensure that the plugin and the Kubernetes clusters are in sync, the plugin polls the Kubernetes API server at a configured interval and listens for notifications from the Kubernetes Watch API at a predefined interval.After you add the cluster information, Panorama always retrieves the such as service, node, replica set and creates tags for them to enable you to gain visibility and to control traffic to and from these clusters. Optionally, you can specify whether you want Panorama to retrieve information on the Kubernetes labels and create tags for these also. See IP-Address-to-Tag Mapping of Kubernetes Attributes for a list of supported attributes.
- Check the monitoring interval.The default interval at which Panorama polls the Kubernetes API server endpoint is 30 seconds.
- Verify thatEnable Monitoringis selected.
- Click the gear icon to edit theMonitoring Intervaland change to a range of 30-300 seconds.
- Select, andPanoramaPluginsKubernetesSetupClusterAdd Cluster.Make sure that you do not add the same Kubernetes cluster to more than one Panorama (single instance or HA pair) appliance because you may see inconsistencies in how the IP-address-to mappings are registered to the device groups.
- Enter aNameand theAPI Server Address.This is the Endpoint IP address for the cluster that you must get from your Kubernetes deployment. Enter a name, up to 20 characters, to uniquely identify the name of the cluster. You cannot modify this name because Panorama uses the cluster name when it creates tags for the pods, nodes, services it discovers within the cluster.The format of the API server address can be a hostname or an IP address:port number, and you do not need to specify the port if you are using port 443, which is the default port.
- Select theTypeof environment on which your cluster is deployed.The available options are AKS, EKS, GKE, Native Kubernetes, OpenShift, and Other.
- Upload the service accountCredentialthat Panorama requires to communicate with the cluster. As described in the Create Service Accounts for Cluster Authentication workflow, the filename for this service account isplugin-svc-acct.json.If you are uploading the service credentials via CLI/API then you must gzip the file and then do a base64 encoding of the compressed file before you upload or paste the contents of the file into the Panorama CLI or API. These steps are not required if you are uploading the service credential file on the GUI.
- ClickOK.You can leave the Label Filter and Label Selector configuration for later. This is an optional task that enables you to retrieve any custom or user-defined labels for which you want Panorama to create tags.
- (Optional) If your Kubernetes cluster API-server certificate is signed by a certificate chain, the authentication from the Kubernetes plugin for Panorama requires every certificate in the chain. If your API server uses a certificate chain, you must combine all the certificates in the chain into a single .crt file and add to the plugin.The Kubernetes plugin supports up to four certificates.
- Selectto import a credentials file.PanoramaKubernetesSetupClusterAddCustom CertificateAdd
- Enter a descriptiveName.
- (Optional) Enter aDescription.
- Click the import icon and navigate to the certificate file.
- (Optional) Configure a proxy for each cluster.Unlike the other plugins, the Kubernetes plugin does not use the proxy configured under. Instead if you want to enable or bypass a proxy, you must enter the proxy for each cluster. When configured, the Kubernetes plugin uses this proxy server IP address to make all API calls to the API server for this cluster.PanormaSetupServices
- Log in to the CLI on Panorama.
- Enter the following CLI commands to configure the proxy server for this Kubernetes cluster.>configure> set plugins kubernetes setup cluster-credentials <cluster-name> cluster-proxy enable-proxy <yes/no> proxy-port <port> proxy-server <IP> proxy-user <username> secure-proxy-password <password>*** username and password are optional ***
Recommended For You
Recommended videos not found.