Hermes Memory Installer is a utility for deploying and managing memory sidecar modules in containerized environments, commonly used alongside Kubernetes workloads. These modules handle tasks such as memory profiling, leak detection, and allocation tracking, running as sidecars to application containers. In the latest release, a critical fix addresses how these modules are loaded, enabling them to be sourced from runtime scripts rather than static configuration alone. This change improves flexibility for dynamic deployments.
The Problem
Previously, the installer loaded memory sidecar modules based on a static list defined in configuration files or environment variables during initialization. This approach required modules to be predetermined at build time or image creation, leading to several issues:
Inflexibility: Changing modules for different environments (e.g., dev vs. prod) meant rebuilding images or maintaining multiple configuration overlays.
Operational Overhead: Deployments with varying memory monitoring needs across nodes or clusters required complex scripting outside the installer.
