Uninstall the Kubernetes Plugin on Panorama
Table of Contents
11.0
Expand all | Collapse all
-
- CN-Series Key Concepts
- CN-Series Core Building Blocks
- Components Required to Secure Kubernetes Clusters with CN-Series Firewall
- CN-Series Deployment—Supported Environments
- CN-Series System Requirements
- Quickstart- CN-Series Firewall Deployment
- CN-Series Performance and Scaling
- Additional CN-Series Resources
-
- CN-Series Deployment Checklist
- CN-Series Prerequisites
- Install a Device Certificate on the CN-Series Firewall
- Create Service Accounts for Cluster Authentication
- Install the Kubernetes Plugin and Set up Panorama for CN-Series
- Get the Images and Files for the CN-Series Deployment
- Editable Parameters in CN-Series Deployment YAML Files
- Enable Horizontal Pod Autoscaling on the CN-Series
- Secure 5G With the CN-Series Firewall
- Enable Inspection of Tagged VLAN Traffic
- Enable IPVLAN
- Uninstall the Kubernetes Plugin on Panorama
- Features Not Supported on the CN-Series
-
- CN-Series HSF System Requirements
- Configure Traffic Flow Towards CN-Series HSF
- Test Case: Layer 3 BFD Based CN-GW Failure Handling
- View CN-Series HSF Summary and Monitoring
- Validating the CN-Series HSF Deployment
- Custom Metric Based HPA Using KEDA in EKS Environments
- Features Not Supported on the CN-Series
Uninstall the Kubernetes Plugin on Panorama
Review the workflow to uninstall the Kubernetes plugin
on Panorama so that you can successfully return all tokens to the
Palo Alto Networks licensing servers.
Use the following workflow to uninstall the
Kubernetes plugin on Panorama so that you can successfully return
all tokens to the Palo Alto Networks licensing servers, and then clear
the authcode. This workflow enables you to ensure that the tokens
are available for use on another Panorama.If you have deployed your
Panorama management server in a high-availability configuration,
you must complete the steps on the active-primary Panorama before
you move to the passive-primary Panorama peer.
- Log in to your active-primary Panorama peer, if deployed in an HA configuration.
- Remove all the cluster configuration from the plugin.
- Delete the monitoring definitions.Select, select the monitoring definitions andPluginsKubernetesMonitoring DefinitionDelete.
- Delete the Kubernetes cluster definitions.Select, select the cluster definitions andPluginsKubernetesSet upClusterDelete.
- Commit your changes on Panorama..CommitCommit to Panorama
- Verify that the used tokens count is zero.To confirm that all the tokens are returned back to the licensing server.
- Perform a clear authcode and make sure the license column authcode is None.
- Remove configuration and commit your changes.
- SelectPluginsand find the Kubernetes plugin version you have installed, andRemove Config.
- .CommitCommit to Panorama
- Uninstall the Kubernetes plugin.
- Suspend the active Panorama peer.Select, and then clickPanoramaHigh AvailabilitySuspend local Panoramalink in the Operational Commands section.
- Log in to your other Panorama peer.Now this peer is the active-secondary peer.
- SelectPluginsand find the Kubernetes plugin version you have installed, andRemove Config.
- Uninstall the plugin.
- SelectPluginsand find the Kubernetes plugin version you have installed, andUninstall.
- Verify that the uninstall was successful.
Clear the Auth Code for the CN-Series Firewalls on Panorama
Use the workaround listed below only if you
removed the plugin configuration and committed your changes before
clearing the authcode. This workaround enables you to release the
toekns back to the licensing server so that you can use it on another Panorama
appliance.
- 1. Add a new plugin user and commit your changes.
- Select.PanoramaAdministrators
- Adda new user called__kubernetes.
- .CommitCommit to Panorama
- Clear the auth code on Panorama.
- Select.PanoramaPluginsKubernetesSetupLicenses
- SelectActivate/update using authorization code, andClear Auth Code.
- Verify that the license column displays auth codeNone.
- Delete the plugin user__kubernetesyou created in Step 1.
- Commit your changes.
- Uninstall the plugin.
- SelectPluginsand find the Kubernetes plugin version you have installed, andUninstall.
- Verify that the uninstall was successful.