Gap
Flux Operator v0.53 introduced step-based reconciliation for ResourceSets (spec.steps — an ordered list of named steps reconciled in sequence, mutually exclusive with resources/resourcesTemplate). Our vendored CRD and generated models already include the field, but nothing in the TUI surfaces it: a multi-step ResourceSet looks identical to a flat one, and there is no way to see which step is in progress or which step failed.
What should happen
References
Sequencing
Independent — nothing blocks it and it blocks nothing. Small scope; good first pick. Complementary to #204 (ResourceSet inventory in the graph); neither blocks the other.
Suggested order: #193 → #192 → #204 → #194 → #195 → #197 → #196 (#198 is ongoing tracking; #191 ✅ shipped in 0.11.0)
Gap
Flux Operator v0.53 introduced step-based reconciliation for ResourceSets (
spec.steps— an ordered list of named steps reconciled in sequence, mutually exclusive withresources/resourcesTemplate). Our vendored CRD and generated models already include the field, but nothing in the TUI surfaces it: a multi-step ResourceSet looks identical to a flat one, and there is no way to see which step is in progress or which step failed.What should happen
References
spec.steps)crds/flux-operator-resourcesets.crds.yamlSequencing
Independent — nothing blocks it and it blocks nothing. Small scope; good first pick. Complementary to #204 (ResourceSet inventory in the graph); neither blocks the other.
Suggested order: #193 → #192 → #204 → #194 → #195 → #197 → #196 (#198 is ongoing tracking; #191 ✅ shipped in 0.11.0)