v4.2.0

Release 4.2.0

Improvements

• Enhanced Argus to discover and add devices with same name across different namespaces
• Collecting Kubernetes version and Argus chart version as kind of telemetry on device group property - cluster device group will be used to store this info.
• Periodically synchronising Devices on LogicMonitor platform with its corresponding kubernetes resource. If kubernetes resource no more exists, Argus will remove the device from LogicMonitor platform.
• User may install LM Container solution using Spinnaker pipeline

Fixes

• Fixed bug to not to allow pod device without system.ips property. This property cannot be updated later on so Argus will not add device until the ip would be available for pod.

Upgrade Steps

• Important: While upgrading Argus chart from older versions to 0.14.0 or higher, you need to pass argus configuration file in helm upgrade command. Follow these steps to create configuration file:
  • Download configuration file template from here
  • Get existing values using command helm get values argus and save in backup configuration file.
  • Put all existing values in downloaded configuration file at its appropriate places. And let the remaining values at their default.
• Upgrade helm charts to the new release (helm repo update) - argus chart version 0.15.0 and collectorset-controller chart version 0.9.0
  • Run helm repo update and followed by upgrade helm upgrade --reuse-values -f argus-config.yaml argus logicmonitor/argus
• Recreate Argus, Collectorset-controller pods if they don't recreate automatically. Helm does not recreate pods if there is no change in definitions.