Support for OpenShift 4.20
LM Container Chart version 13.2.0 is now certified for compatibility with OpenShift 4.20. For more information, see Support Matrix for Kubernetes Monitoring.
Helm v4 Support for Argus Upgrades
Argus now supports Helm v4 upgrades. You can now upgrade existing Argus deployments, including version 12.1.1 or later, without upgrade failures related to Helm v4 compatibility.
Added Security Updates
LogicMonitor has added security updates to the internal components of LM Container.
End of Life (EOL) for Legacy Versions 5, 6, 7, and 8 for LM Container and Argus
In a future release of LogicMonitor, support for legacy LM Container builds and Argus versions 5, 6, 7, and 8 will be discontinued. If you are running these versions, upgrade to a supported LM Container release to continue receiving updates and support.
The latest LM Container releases provides the following benefits:
- Improved monitoring accuracy using updated and actively maintained code paths
- The latest security patches and compliance updates required for modern Kubernetes environments
- Ongoing compatibility with newer Kubernetes versions and container runtimes
If your LM Container installation is running Argus version 8 or later, use the LM Upgrade Wizard or the CLI to complete the upgrade.
For Argus version 7 or earlier, migrate these deployments to LM Container before upgrading. You can migrate existing Kubernetes cluster configurations using either of the following procedures in the product documentation:
Running a supported LM Container version ensures continued compatibility with newer Kubernetes versions and container runtimes and preserves active LogicMonitor support.
For more information about this deprecation, including timeline details and further removal updates, see Upcoming End of Life (EOL) for Legacy Versions 5, 6, 7, and 8 for Legacy LM Container & Argus in the LM Community.
If you have any questions or need assistance during this transition, contact the Support team or your Customer Success Manager.
Fixed an issue that prevented lm-container from deploying and running the Collector successfully when argus.replicas=0 was configured in lm-container-13.1.0. The Collector now deploys, registers, and collects data successfully when Argus is disabled.
Next Steps
For more information on the upgrade procedure, see Upgrading LM Container Charts in the product documentation.
