Skip to content

v1.6.0

Choose a tag to compare

View all tags
@gianlucam76 gianlucam76 released this 09 Mar 20:56
· 2 commits to release-1.6 since this release
v1.6.0
bb9f7f5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

🚀 Release Notes: Performance & Stability Update

This release focuses heavily on infrastructure efficiency and core stability. We have significantly optimized the resource footprint of our edge components and addressed several critical bugs in the addon-controller.

⚡ Performance Optimizations

We have optimized the resource management for sveltos-agent and drift-detection-manager. These components are now leaner and more efficient, particularly in large-scale environments.

  • Memory Efficiency: Drastically reduced memory consumption, specifically targeting system admin memory overhead. This ensures a smaller footprint on managed nodes.
  • CPU Optimization: Refined execution loops to lower CPU cycles during idle and reconciliation phases.

🐞 Bug Fixes

This version resolves several edge-case behaviors and stability issues:

  • #1635: Clean up Stale ResourceSummaries (Agentless): Fixed an issue in agentless mode where ResourceSummary objects were not being properly cleaned up, leading to stale data in the management cluster.

  • #1632: Resolve Helm Installation Deadlock: Addressed a critical bug where Helm installations could enter a deadlock state, preventing the deployment from moving forward.

  • #1630: Fix Drift Detection Upgrade (Agentless): Resolved a failure during the upgrade process of the drift detection mechanism when running in agentless mode.

✨ Improvements

  • #1625: New FailedClusters Status Field: Surfaced orchestration-level errors (e.g., failure to create/update a ClusterSummary) directly in the ClusterProfile status. This eliminates "blind spots" where users previously had to check controller logs to understand why a profile wasn't progressing.

  • #1620: Specialized Health Check Error Handling: * Introduced a dedicated HealthCheckError type to distinguish between deployment failures and functional health check failures. Added the --health-error-retry-time CLI flag (default: 90s). This allows the controller to back off specifically on health failures without affecting standard reconciliation requeue logic.

Assets 2
Loading