(feat) Add **FailedClusters** to ClusterProfile/Profile Status#1625
Merged
gianlucam76 merged 1 commit intoprojectsveltos:mainfrom Feb 24, 2026
Merged
Conversation
This PR improves observability for orchestration failures by adding a new **FailedClusters** field to the ClusterProfile (and Profile) status. Previously, the visibility of deployment errors was split: - Deployment errors (Helm, YAML application) are reported in the ClusterSummary status. - Orchestration errors (failure to create or update a ClusterSummary instance itself) were only visible in the addon-controller logs. This created a "blind spot" where users couldn't easily tell why a matching cluster had no associated ClusterSummary or why a profile wasn't progressing for a specific cluster. The FailedClusters field now tracks these "pre-deployment" errors. If the controller fails to update a ClusterSummary for a matching cluster, it captures the error message and the cluster reference directly in the Profile's status. - Added FailedClusters slice to the Status struct. - Implemented logic to populate/clear errors during the ClusterSummary reconciliation loop. - Improved troubleshooting speed by surfacing orchestration-level blockers in the API.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR improves observability for orchestration failures by adding a new FailedClusters field to the ClusterProfile (and Profile) status.
Previously, the visibility of deployment errors was split:
This created a "blind spot" where users couldn't easily tell why a matching cluster had no associated ClusterSummary or why a profile wasn't progressing for a specific cluster.
The FailedClusters field now tracks these "pre-deployment" errors. If the controller fails to update a ClusterSummary for a matching cluster, it captures the error message and the cluster reference directly in the Profile's status.