fix: reflect blocked teardown as Blocked in featureSummaries status - #1953
Merged
Conversation
ClusterSummary.status.featureSummaries[].status stayed did not move to Removing whenever teardown
was deferred by either a still-existing DependsOn dependent, or a TransitionFrom successor not yet
Provisioned.
status.dependencies correctly explained the wait, but status kept implying active work, which is misleading.
Adds a FeatureStatusBlocked value to the shared FeatureStatus and sets it.
The ClusterSummary Status will explain whats happening
```yaml
status:
dependencies: ClusterProfile deploy-kyverno-v2 is replacing this profile on this
cluster but is not fully deployed yet
featureSummaries:
- featureID: Helm
lastAppliedTime: "2026-09-09T14:20:22Z"
resourceSummaryDeployed: false
status: Blocked
```
Fixes projectsveltos#1950.
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.
ClusterSummary.status.featureSummaries[].status stayed did not move to Removing whenever teardown was deferred by either a still-existing DependsOn dependent, or a TransitionFrom successor not yet Provisioned.
status.dependencies correctly explained the wait, but status kept implying active work, which is misleading.
Adds a FeatureStatusBlocked value to the shared FeatureStatus and sets it.
The ClusterSummary Status will explain whats happening
Fixes #1950.