Version 102 of the Kubernetes PowerPack includes new collection objects, a new presentation object, new Dynamic Applications, a new icon, and updates to no longer require the Docker PowerPack to use the Kubernetes PowerPack.
- Minimum Required SL1 Version: 8.12.2.6
Before You Install or Upgrade
Ensure that you are running version 8.12.2.6 or later of SL1 before installing "Kubernetes" PowerPack version 102.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
In addition, before installing or upgrading the PowerPack, you must first import and install the Linux Base Pack PowerPack version 103, which leverages this PowerPack.
If you are upgrading from version 101 to version 102 of the PowerPack, you must delete the version 101 dashboards on SL1. To do so, perform the following steps:
- Go to the Device Dashboards page (System > Customize > Device Dashboards).
- Search for "Kubernetes" in the Device Dashboard Name column.
- Select the checkbox for each Kubernetes dashboard.
- In the Select Actions drop-down field, select Delete Dashboards.
- Click the button.
- Click the button to confirm.
Installation and Upgrade Process
To install this PowerPack:
- Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
- In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
- Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
- Click and navigate to the PowerPack file from step 1.
- Select the PowerPack file and click . The PowerPack Installer modal displays a list of the PowerPack contents.
- Click . The PowerPack is added to the PowerPack Manager page.
NOTE: If you are upgrading from version 100 or greater of the Kubernetes PowerPack, install the DockerPowerPack version 102 or greater before upgrading, if you have not done so already.
For more information about using the PowerPack, see the Monitoring Kubernetes manual.
Features
This release includes the following features:
- Dynamic Applications to discover and monitor Kubernetes devices
- Device Classes for each of the Kubernetes devices the PowerPack can monitor
- Event Policies and corresponding alerts that are triggered when Kubernetes devices meet certain status criteria
- A Dashboard and Dashboard Widget that you must use to create Credentials for discovering Kubernetes devices
- An SSH/Key Credential that the Kubernetes Token Entry Dashboard uses as a template for creating additional SSH/Key Credentials for monitoring Kubernetes clusters
You must use the Kubernetes Token Entry Dashboard that is included in the PowerPack to create a master SSH/Key Credential, a node SSH/Key Credential, and a SOAP/XML Credential that enables you to specify the Kubernetes device topology that you want to discover. For more information, see the Monitoring Kubernetes manual.
You must not edit the SSH/Key Credential that is included in the PowerPack.
- Run Book Action and Automation policies that do the following:
- Automatically create Kubernetes clusters whenever the ScienceLogic platform discovers a Kubernetes host
- Align Dynamic Applications from the Linux Base Pack PowerPack to Kubernetes nodes and report back to the ScienceLogic Data Collector or All-in-One Appliance if the Dynamic Applications were successfully aligned
- Ensure that Namespaces (and their children) have a 1-hour vanishing timer, to properly reflect topology changes
Enhancements and Issues Addressed
The following enhancements and addressed issues are included in version 102 of the "Kubernetes" PowerPack:
- The Docker PowerPack is no longer required to use the Kubernetes PowerPack.
- The cache list was updated with improved URLs.
- The following Dynamic Applications were added to the PowerPack:
- Kubernetes: Horizontal Pod Autoscaler Configuration
- Kubernetes: Ingress Controller Discovery
- Kubernetes: Ingress Controller Configuration
- Summarization state has been enabled for all Kubernetes Performance Dynamic Applications.
- The "% Successful Requests" presentation object was added to the "Kubernetes: Self Monitoring Performance" Dynamic Application.
- A new icon was added to the "Kubernetes: Ingress Controller Discovery" Dynamic Application.
- The "Horizontal POD Autoscale Count" collection object was added to the "Kubernetes: Controller Performance" Dynamic Application.
- The following collection objects were added to the "Kubernetes: Controller Pod Performance" Dynamic Application:
- CPU
- Memory
The "Pod Count" and "Container Restart Count" collection objects were added to the "Kubernetes: Controller Performance" Dynamic Application. ScienceLogic recommends you delete the Collection Objects from the "Kubernetes: Controller Pod Performance" Dynamic Application. For more information on deleting collection objects from a Dynamic Application, see the "Performing Bulk Actions on Collection Objects" section in the Collection Objects chapter in the Dynamic Application Development manual.
- The following Dynamic Applications are now automatically aligned to this PowerPack by Run Book Actions:
- Linux: IC Availability
- Linux: IC Detail
- Linux: IC Filesystem Inventory
- Linux: IC Filesystem Performance
- Linux: IC Interface Inventory
- Linux: IC Interface Performance
- Linux: IC Port Performance
- Linux: IC Process Inventory
- Linux: IC Process Performance
- Linux: ICDA Cache
- Linux: ICDA Interface Cache
- The following Dynamic Applications will no longer be automatically aligned by Run Book Actions. The information collected and presented by these Dynamic Applications will now be collected and presented by the Internal Collection Dynamic Applications that are now automatically aligned to this PowerPack:
- Linux: File System Performance
- Linux: Interface Performance
- Linux: Network Configuration
- Linux: TCP Services
If you would like to use these Dynamic Applications, you may do so by aligning them to a device manually or using a template.
- The "Kubernetes: Docker Aggregate Container Performance" Dynamic Application was removed from the PowerPack.
If you are upgrading from version 100 or greater to version 102 of the Kubernetes PowerPack, ScienceLogic recommends you delete the "Kubernetes: Docker Aggregate Container Performance" Dynamic Application from your SL1 system. For more information on deleting Dynamic Applications, see the "Performing Other Tasks in the Dynamic Application Manager Page" section in the Managing Dynamic Applications chapter in the Dynamic Application Development manual.
- An issue was addressed in the "Kubernetes: Node Discovery" Dynamic Application in which an exception was occurring when the Dynamic Application was run in Debug mode.
- An issue was addressed in which incorrect events were being generated when running the "Kubernetes: Persistent Volume Configuration" Dynamic Application.
- An issue was addressed in which an unhandled exception was occurring when running the "Kubernetes: Controller Pod Configuration" Dynamic Application.
- An issue was addressed in which the "Kubernetes: Cluster Creation" event was triggered multiple times.
- An issue was addressed in which the "Kubernetes Component Count" Dynamic Application was showing 0 total EM7 components.
-
An issue was addressed in which an exception was occurring when running Kubernetes Configuration and Performance Dynamic Applications.
Known Issues
The following known issues affect version 102 of the Kubernetes PowerPack:
- Users can discover Elastic Kubernetes Service (EKS) and Google Kubernetes Engine (GKE) clusters with the PowerPack, but full support and testing for EKS and GKE has not yet been implemented.
- When using SL1 platform version 8.14.0 with this PowerPack, Kubernetes device discovery will fail and is not recommended to use this version of the PowerPack. SL1 platform version 8.14.1 and later accurately discovers Kubernetes devices.
- The KubernetesPowerPack includes a widget that is required to setup credentials for Kubernetes devices. The widget writes the credentials directly to the database. In SL1 platform version 10.1.6 and later, the credentials can no longer be accessed directly from the database. Users that upgrade to SL1 platform version 10.1.6 or later will not be able to create credentials and discover any new Kubernetes devices. Users will also not be able to change the credentials for any Kubernetes devices that have already been discovered. This issue will be addressed in a later release.