chore(deps): bump github.com/projectsveltos/addon-controller from 1.1.1 to 1.2.1

[dependabot]

Bumps github.com/projectsveltos/addon-controller from 1.1.1 to 1.2.1.

Release notes

Sourced from github.com/projectsveltos/addon-controller's releases.

v1.2.1

✨ New Features and Enhancements

Dashboard Enhancements

• Filter deployed resources by namespace, name, kind
• Filter deployed Helm charts by release namespace and name
• Filter Profiles by namespace, name
• Display when cluster is paused

Health Check Enhancement

• When a resource is detected as degraded, a Kubernetes Events will be generated in the managed cluster (on the resource itself)
• Instruct the sveltos-agent to re-evaluate a HealthCheck rule for a specific duration before setting a status to Degraded. This is useful for scenarios like detecting a Pod using stale Secret data, allowing time for the Pod to naturally update or restart.

🐛 Bug Fixes and Enhancements

• Fix a crash in addon-controller for clusters in pull mode when KustomizationRefs are used. PR
• Fix Reloader with Secrets
• Extend agent overrides: Any resource can now be overridden

v1.2.0

✨ New Features and Enhancements

Progressive Rollouts with Cluster Promotion

A new Custom Resource Definition (ClusterPromotion) is introduced to enable declarative, multi-stage, progressive rollout of a single configuration (profileSpec) across multiple sets of clusters. This is ideal for promoting configurations from environments like staging to production in a controlled, sequential manner.

It manages an ordered series of stages, each with its own cluster selector.

It supports automated promotion to the next stage after the previous stage's configuration is successfully deployed (e.g., waiting for a defined delay).

See [PR #1437](projectsveltos/addon-controller#1437)

Enhanced Conflict Resolution and Metadata Handling

Policy Tier for Conflict Resolution

The new Tier field has been added to PolicyRef and KustomizationRef objects. This introduces a secondary, intra-profile priority system designed to resolve resource conflicts.

When multiple ClusterProfile or Profile objects targeting the same cluster attempt to deploy the identical Kubernetes resource, the ClusterProfile with the lowest numerical Tier value wins (lower number indicates higher priority).

See [PR #1439](projectsveltos/addon-controller#1439)

🐛 Bug Fixes and Enhancements

1. Optimized Reconciliation Logic PR 1398:

Resolved an issue that caused unnecessary reconciliation loops for add-on profiles, leading to excessive resource consumption and potential rate-limiting. The controller now only reconciles when actual changes occur.

2. Prevented Controller Crash PR 1407:

... (truncated)

Commits

• fd9124e Merge pull request #1486 from gianlucam76/release-1.2
• 869fc7a (chore) prepare for release v1.2.1
• 32a3566 Merge pull request #1482 from gianlucam76/release-1.2
• fb3a72b (feat) Enhance applier and agent patches
• 93c8d73 Merge pull request #1480 from gianlucam76/release-1.2
• 2930be5 Lua options
• a2e107e Merge pull request #1478 from gianlucam76/release-1.2
• c5405d3 Update Helm release nginx-stable/nginx-ingress to v2.3.1
• dca08cd (feat) Pass reference resource info to applier
• 31a60cc Merge pull request #1475 from gianlucam76/release-1.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)