Known Issues in Kubernetes Plugin 3.0.0
Table of Contents
Expand all | Collapse all
-
-
-
-
- Features Introduced in Zero Touch Provisioning 2.0
- Known Issues in the Zero Touch Provisioning 2.0.4 Release
- Known Issues in the Zero Touch Provisioning 2.0.3 Release
- Known Issues in the Zero Touch Provisioning 2.0.2 Release
- Known Issues in the Zero Touch Provisioning 2.0.1 Release
- Known Issues in the Zero Touch Provisioning 2.0.0 Release
- Limitations
-
-
Known Issues in Kubernetes Plugin 3.0.0
The following list describes known issues
in the Panorama plugin for Kubernetes version 3.0.0.
PLUG-9648
In HA paired Panoramas, the authcode used in Kubernetes setup on Primary Panorama is not copied to Secondary Panorama due to synching issues with the Database.
Workaround: If the authcode is not synced between the HA pair, add the authcode again on the secondary Panorama.
PLUG-9656
The Kubernetes plugin License information
is not synced between the HA paired Panaromas.
PLUG-9782
If the monitoring-definition goes into
failure state in cases where a proxy is used for the Kubernetes
plugin, the cluster validation status is not updated based on failed
proxy connectivity.
Workaround: Check the plugin logs for the updated service
credentials validation status from Panorama CLI using the command:
tail follow yes plugins-log plugin_kubernetes_tag_ret.log