📖 align ClusterObjectSet concept doc with the single Ready condition

[perdasilva]

Description

Align the ClusterObjectSet concept doc with the current single Ready condition model.

The ClusterObjectSet reports only a Ready condition; the Progressing and Succeeded conditions were removed, and rollout completion is tracked by the status.completedAt timestamp. This updates docs/draft/concepts/clusterobjectsets.md accordingly:

• Drop the stale Progressing and Succeeded condition sections.
• Add a Completion (status.completedAt) section.
• Remove the Migrated Ready-reason row (no such reason is emitted).
• Add the ProgressDeadlineExceeded Ready-reason row, which the controller emits and the API doc-string already documents but the concept table was missing.
• Reword "reports Succeeded" references in the transition/upgrade flows to "rolled out successfully".

The Ready-reason table now matches the API doc-string's reason set exactly (AllObjectsReady, ObjectsNotReady, Superseded, ObjectCollision, PreconditionsNotMet, InvalidSpecification, ProgressDeadlineExceeded, Archiving, Archived) — reflecting the ValidationFailure → PreconditionsNotMet/InvalidSpecification split (#3017) and the RetryableError removal (#3012), both now in main.

Docs-only change.

Supersedes #3003 (rebased onto main; the original was part of a now-merged stack).

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated cluster object set guidance to allow the previous revision to be archived after the new revision rolls out successfully, without requiring a Succeeded status.
  • Clarified that rollout completion is recorded separately from readiness. The completion timestamp is set the first time a revision becomes ready, persists if readiness is later lost, and does not change.
  • Revised the status conditions guidance to describe a single Ready condition, add the ProgressDeadlineExceeded reason, and remove the separate Succeeded condition and Migrated reason.

[netlify]

✅ Deploy Preview for olmv1 ready!

Name	Link
🔨 Latest commit	d32da54
🔍 Latest deploy log	https://app.netlify.com/projects/olmv1/deploys/6ad239ea207a6582b80b5d64
😎 Deploy Preview	https://deploy-preview-3021--olmv1.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Enterprise
• Run ID: ae7db20a-690b-4d74-b7f4-bb0feec6149b

📥 Commits

Reviewing files that changed from the base of the PR and between c2d7203 and d32da54.

📒 Files selected for processing: 1

• docs/draft/concepts/clusterobjectsets.md

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

📝 Walkthrough

The ClusterObjectSet documentation now describes rollout completion through status.completedAt and uses successful rollout as the criterion for archiving an old revision.

Changes: Revision status and archival

Layer / File(s)	Summary
Readiness and archival guidance docs/draft/concepts/clusterobjectsets.md	The documentation describes one Ready condition and the status.completedAt timestamp. It updates the archival criterion to successful rollout and removes the Migrated reason and Succeeded condition descriptions.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: fao89

Merge Risk: ⚪ Minimal · up to d32da

This documentation update accurately describes successful rollout, archival, and readiness status. No actionable mergeability risk remains.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly identifies the documentation change and its alignment with the single Ready condition model.
Description check		The description explains the documentation changes, motivation, affected API concepts, related issues, and confirms that the change is docs-only. It omits the reviewer checklist from the template, but…
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description explains the documentation changes, motivation, affected API concepts, related issues, and confirms that the change is docs-only. It omits the reviewer checklist from the template, but the main required change information is complete.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[fgiudici]

/lgtm

[joelanford]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelanford

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• docs/draft/OWNERS [joelanford]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

New changes are detected. LGTM label has been removed.