Addressed Issues in Kubernetes Plugin 1.0.1
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
-
-
Addressed Issues in Kubernetes Plugin 1.0.1
The following list describes addressed
issues in the Panorama plugin for Kubernetes, version 1.0.1.
PLUG-5519
When the node IP address is the same
as the IP address for the pan-cni, kube-proxy, or other components
that enable pod networking, the IP-tag mappings were not generated.With
this fix, IP-tag mappings are generated so that you can enable Dynamic
Address Groups and enforce policy to allow or deny traffic.
This issue is fixed in version 1.0.1.
PLUG-5382
When you provide the cluster API server
address on KubernetesSetupAPI server address. if you
append an extra space after the IP address, the poller/watcher remains
in a disconnected state although the credentials are accurate.
With this fix, the extra space at the end of the
IP address is removed on commit, ensuring 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 the predefined interval.
This issue is fixed in version 1.0.1.
PLUG-4719
With this fix, you can manually upload
the license key on the Kubernetes plugin for Panorama (PanoramaPluginsKubernetesSetupLicenses.
This issue is fixed in version 1.0.1.