Skip to content

Conversation

gianlucam76
Copy link
Member

Before this fix, template errors (in PolicyRefs,
KustomizationRefs, or HelmCharts) caused a poor user experience:

  1. The ClusterSummary Status was never updated, hiding the error from the resource status (visible only in logs).
  2. The controller continuously returned a retryable error, causing the ClusterSummary to be aggressively reconciled followed by long, unpredictable delays.

This PR improves stability and visibility by:

  1. Setting the ClusterSummary Status with the precise template error.
  2. Reporting the error as non-retryable to stop the aggressive requeueing.

This approach ensures the system doesn't waste resources constantly processing an unfixable error, requiring the user to explicitly update the ClusterProfile to resolve the issue.

While some template errors might auto-resolve (e.g., a missing Cluster label being added), preventing constant requeueing is the preferred, stable behavior.

Before this fix, template errors (in PolicyRefs,
KustomizationRefs, or HelmCharts) caused a poor user experience:

1. The ClusterSummary Status was never updated, hiding the error
from the resource status (visible only in logs).
2. The controller continuously returned a retryable error, causing
the ClusterSummary to be aggressively reconciled followed by long,
unpredictable delays.

This PR improves stability and visibility by:

1. Setting the ClusterSummary Status with the precise template error.
2. Reporting the error as non-retryable to stop the aggressive requeueing.

This approach ensures the system doesn't waste resources constantly
processing an unfixable error, requiring the user to explicitly update
the ClusterProfile to resolve the issue.

While some template errors might auto-resolve (e.g., a missing Cluster
label being added), preventing constant requeueing is the preferred,
stable behavior.
@gianlucam76 gianlucam76 merged commit f1991d2 into projectsveltos:release-1.1 Oct 4, 2025
8 checks passed
@gianlucam76 gianlucam76 deleted the release-1.1 branch October 4, 2025 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant