Skip to content

chore(deps): update dependency projectsveltos/sveltosctl to v1.6.0#170

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/projectsveltos-sveltosctl-1.x
Open

chore(deps): update dependency projectsveltos/sveltosctl to v1.6.0#170
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/projectsveltos-sveltosctl-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 13, 2025

This PR contains the following updates:

Package Update Change
projectsveltos/sveltosctl minor 1.2.11.6.0

Release Notes

projectsveltos/sveltosctl (projectsveltos/sveltosctl)

v1.6.0

Compare Source

🚀 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.

v1.5.1

Compare Source

🐞 Bug Fixes

  • Fix ClusterSummary hash evaluation when running with agents in the management cluster. PR

  • Honor Kubernetes cluster domain PR

v1.5.0

Compare Source

✨ New Features & Enhancements

  1. Pre and Post-Delete Validation Checks (#​1590): Introduces the ability to define health checks that must pass before and after a resource is deleted. This ensures that addons are only removed when the cluster is in a safe state and verifies that the removal was successful and didn't leave the system in an unstable condition.

  2. Dynamic Patches via patchesFrom (#​1585): Profiles and ClusterProfiles can now reference ConfigMaps or Secrets containing StrategicMerge or JSON patches.

  • Templating Support: The name and namespace of the referenced resource can be defined using templates (e.g., {{ .Cluster.metadata.name }}-patches), allowing for cluster-specific patches managed centrally.
  • Flexible Formats: Supports both standard Kubernetes strategic merge patches and JSON patches (RFC 6902).

⚡ Optimizations

  1. Agent Efficiency: Optimized memory utilization across Sveltos agents, reducing the overhead for both sveltos-agent and drift-detection-manager

  2. Log Refinement: Reduced log noise in info mode. High-volume, non-essential logs have been suppressed to provide a clearer view of system health and deployment progress.

🐞 Bug Fixes

  1. Fixed Accidental Helm Uninstalls on Restart (#​1608): Resolved a critical issue where templated Helm release names or namespaces caused the Chart Manager to incorrectly identify releases as "stale" during controller restarts. This fix ensures that templated values are properly instantiated before being compared against existing releases, preventing accidental uninstalls.

  2. Race Condition Protection in Request Queue (#​1600): Improved reconciliation reliability by discarding results if a newer request for the same key is already in the dirty queue. This ensures the controller always acts on the most recent cluster state and prevents outdated results from overriding newer pending changes.

v1.4.0

Compare Source

This release introduces significant enhancements to the Sveltos Dashboard, providing deeper visibility into event-driven workflows, and brings critical performance optimizations to EventReports and Pull-Mode cluster management. We’ve also enhanced the Sveltos MCP Server to simplify debugging of the Sveltos event framework.

✨ New Features & Enhancements

The Dashboard now offers a comprehensive view of your event-driven automation.

  • Visibility: Display all EventTriggers in a single view.
  • Traceability: For each EventTrigger, you can now see the linked EventSource and all matching clusters.
  • Resource Inspection: Drill down into specific clusters to see exactly which Kubernetes resources matched the EventSource.

MCP Server for Framework Debugging

The Sveltos MCP (Model Context Protocol) Server has been enhanced to assist in debugging the Sveltos event framework. This tool provides a structured way to interact with and inspect the internal state of the event engine.

Reference: mcp-server PR #​33

⚡ Performance Optimizations

  1. Smart EventReport Processing

We have optimized how EventReports are handled. Previously, every collected report was reprocessed. Now, Sveltos performs a delta check and only reprocesses EventReports that have changed since the last collection, significantly reducing CPU cycles in the management cluster.

  1. Resilient Pull-Mode Handling

Improved handling for managed clusters in Pull Mode when the Sveltos Agent stops reporting a "keep-alive":

  • Fault Detection: If an agent is non-responsive, Sveltos will skip that cluster and report a specific error: agent is not sending keep alive.

  • Auto-Recovery: As soon as the agent resumes communication, Sveltos automatically reprocesses all resources that were in a faulty state during the downtime.

🛠 Bug Fixes & Improvements

  • Drift-Detection: Fixed a critical issue where the drift-detection-manager failed to detect expired Kubeconfigs when running as an agent in a managed cluster.#​363).

  • Event Manager: Enhanced reliability for event-driven resource distribution (#​436).

  • Event Manager: Improved cleanup and state management within the event manager (#​427).

  • Addon Controller: Various stability fixes and internal logic improvements across PRs #​1572, #​1568, #​1563, and #​1555.

  • Reloader: Fixed an issue where triggered rollouts failed for DaemonSets and StatefulSets when the Reloader knob was enabled.

v1.3.1

Compare Source

🐛 Bug Fixes

Resolved an issue where the drift-detection-manager was being unnecessarily upgraded in managed clusters even when drift detection was not configured (i.e., when a Profile did not use SyncMode: ContinuousWithDriftDetection). The controller now correctly checks for the presence of the ResourceSummary CRD before initiating the drift-detection-manager upgrade.

PR

v1.3.0

Compare Source

✨ New Features and Enhancements

🚀 Promotion Enhancements: Pre-Health Check Deployments

Introduced the optional PreHealthCheckDeployment field to the ClusterPromotion resource. This allows users to deploy and reconcile specific resources—such as validation Jobs or temporary services—after the configured delay but before post-delay health checks are executed. This ensures the environment is fully prepared for validation.

PR

🛠️ Per-Cluster Agent Patches via Annotations

Sveltos now supports granular, per-cluster configuration for its agents. Users can apply unique configuration patches to individual managed clusters using annotations to reference a specific ConfigMap. This is ideal for scenarios requiring cluster-specific overrides, such as using regional private container registries.

Supported Annotations:
  • driftdetection.projectsveltos.io/config-override-ref
  • sveltosagent.projectsveltos.io/config-override-ref
  • sveltosapplier.projectsveltos.io/config-override-ref

PR
PR

🔄 Dependency-Aware Forced Redeployment

Introduced the sveltosctl redeploy cluster command, allowing users to forcefully trigger a re-application of all Sveltos-managed add-ons and resources on a target cluster.

  • Intelligent Execution: Instead of a simple reset, it performs a dependency-aware reconciliation. It uses a topological sort based on the dependsOn field in ClusterSummary resources to ensure prerequisites are reconciled before dependent resources.

  • Benefit: Enables a full configuration refresh or rolling update without requiring any changes to the ClusterProfile or Profile specifications.

PR

📦 Helm: Resource Ownership Adoption (TakeOwnership)

Introduced the TakeOwnership field for Helm chart deployments. This allows Sveltos to manage and adopt resources that already exist in a cluster, even if they lack the standard Helm ownership annotations (meta.helm.sh/release-name, etc.).

Default: false (standard Helm safety checks remain active unless explicitly enabled).
PR

🐛 Bug Fixes and Enhancements

  • Fixed ActiveWindow Reconciliation: Resolved an issue where changes to the ActiveWindow settings in a SveltosCluster resource would not always trigger a correct recalculation of the NextPause and NextUnpause times. This fix ensures that any modification to the ActiveWindow specification forces a re-evaluation of the scheduling. Additionally, the feature now explicitly reads and stores ActiveWindow times using UTC to prevent timezone-related errors in scheduling calculations.
    PR

  • Fixed Drift Exclusion Reconciliation: Fixed a bug where Sveltos would not react to changes in the DriftExclusions field within a ClusterProfile or Profile. This issue prevented Sveltos from correctly updating the set of resources excluded from drift detection when the configuration was modified.
    PR

  • Fixed Stuck Add-on Deletion in Pull Mode: Corrected an issue where, in pull mode, add-on deletion would get stuck if the governing Profile or ClusterProfile was deleted while the resources were still being deployed. This occurred because the local controller attempted deletion while the remote agent's action was still set to deploy. The fix ensures the remote ConfigurationGroup is cleaned up, allowing the deletion to complete.
    PR

⚠️ Important Compatibility & Dependency Updates

🚨 ClusterAPI v1.12.0 (v1beta2) Support: Sveltos has transitioned to ClusterAPI v1.12.0, moving to the v1beta2 API version.

Action Required: To upgrade to this Sveltos release, users leveraging ClusterAPI integration must ensure their management clusters are using v1beta2 ClusterAPI CRDs.

🔄 Automatic Redeployment on Upgrade

Due to the fix for DriftExclusions tracking, the internal hash calculation now includes the driftExclusion field.

Impact: Upon upgrading to this version, any Profile or ClusterProfile that contains populated driftExclusion fields will undergo a one-time automatic redeployment.

Toolchain Updates:

ClusterAPI: v1.12.0
Go: v1.25.5
Helm: v3.19.4


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/projectsveltos-sveltosctl-1.x branch 2 times, most recently from 64fcad8 to 5558e19 Compare December 15, 2025 21:58
@renovate renovate bot changed the title chore(deps): update dependency projectsveltos/sveltosctl to v1.3.0 chore(deps): update dependency projectsveltos/sveltosctl to v1.3.1 Dec 15, 2025
@renovate renovate bot force-pushed the renovate/projectsveltos-sveltosctl-1.x branch 3 times, most recently from c49f66b to 05b0c8e Compare December 31, 2025 10:45
@renovate renovate bot force-pushed the renovate/projectsveltos-sveltosctl-1.x branch from 05b0c8e to 9b9e765 Compare January 10, 2026 08:46
@renovate renovate bot changed the title chore(deps): update dependency projectsveltos/sveltosctl to v1.3.1 chore(deps): update dependency projectsveltos/sveltosctl to v1.4.0 Jan 10, 2026
@renovate renovate bot force-pushed the renovate/projectsveltos-sveltosctl-1.x branch 3 times, most recently from eaab88d to 3b1d6ef Compare January 21, 2026 14:19
@renovate renovate bot force-pushed the renovate/projectsveltos-sveltosctl-1.x branch from 3b1d6ef to 4573542 Compare February 14, 2026 13:53
@renovate renovate bot changed the title chore(deps): update dependency projectsveltos/sveltosctl to v1.4.0 chore(deps): update dependency projectsveltos/sveltosctl to v1.5.0 Feb 14, 2026
@renovate renovate bot force-pushed the renovate/projectsveltos-sveltosctl-1.x branch from 4573542 to cf27d3c Compare February 15, 2026 18:09
@renovate renovate bot changed the title chore(deps): update dependency projectsveltos/sveltosctl to v1.5.0 chore(deps): update dependency projectsveltos/sveltosctl to v1.5.1 Feb 15, 2026
@renovate renovate bot force-pushed the renovate/projectsveltos-sveltosctl-1.x branch 7 times, most recently from 9d38664 to 8f43e5d Compare March 5, 2026 15:39
@renovate renovate bot force-pushed the renovate/projectsveltos-sveltosctl-1.x branch from 8f43e5d to 77dcb10 Compare March 8, 2026 12:56
@renovate renovate bot changed the title chore(deps): update dependency projectsveltos/sveltosctl to v1.5.1 chore(deps): update dependency projectsveltos/sveltosctl to v1.6.0 Mar 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants