docs: Add stateless migration quickstart tutorial#569
Merged
msajidmansoori12 merged 9 commits intoJun 30, 2026
Merged
Conversation
Signed-off-by: M Sajid Mansoori <mmansoor@redhat.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdds a new quickstart doc for Crane stateless migration, covering setup, export, transform, apply, validate, instructions-file usage, and troubleshooting. ChangesStateless Migration Quickstart Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/stateless-migration-quickstart.md`:
- Around line 185-195: The validation summary example is inconsistent with the
JSON report example, since the console snippet says 4 scanned while the report
shows 3 results and totalScanned: 3. Update the example output and any related
validation summary text in the stateless migration quickstart so the
scanned/compatible/incompatible counts match the report example consistently,
including the “Summary” and “Result” snippets tied to the validation flow.
- Around line 189-190: The quickstart sample output uses a different target
context label than the command example, so update the expected output in the
migration doc to use the same `${TARGET_CONTEXT}` value consistently. Locate the
sample log lines that show the live validation context and change the displayed
context name to match the target context used elsewhere in the doc, keeping the
naming aligned in the quickstart flow.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 585b7db4-7898-4132-93cb-ada07330d7d6
📒 Files selected for processing (1)
docs/stateless-migration-quickstart.md
Test Coverage ReportTotal: 46.9% Per-package coverage
Full function-level detailsPosted by CI |
msajidmansoori12
changed the title
msajidmansoori12
force-pushed
the
add-stateless-migration-doc
branch
from
b6b8f09 to
f5d5124
Compare
msajidmansoori12
force-pushed
the
add-stateless-migration-doc
branch
from
f5d5124 to
310487e
Compare
midays
requested changes
Jun 24, 2026
istein1
reviewed
Jun 24, 2026
|
|
||
| In most pipelines, your custom stage is the last stage under `transform/`, so rendering that directory should show the manifests that will feed into the final apply output. | ||
|
|
||
| For a deeper explanation of stage ordering, stage structure, and multi-stage behavior, see [Multi-Stage Kustomize Transform Pipeline](./kustomize-multistage.md). |
|
|
||
| For a deeper explanation of stage ordering, stage structure, and multi-stage behavior, see [Multi-Stage Kustomize Transform Pipeline](./kustomize-multistage.md). | ||
|
|
||
| If a custom stage already contains edits, rerun with `--force` to regenerate: |
Contributor
Author
There was a problem hiding this comment.
Fixed with more clear info
Signed-off-by: M Sajid Mansoori <mmansoor@redhat.com>
Signed-off-by: M Sajid Mansoori <mmansoor@redhat.com>
Signed-off-by: M Sajid Mansoori <mmansoor@redhat.com>
Signed-off-by: M Sajid Mansoori <mmansoor@redhat.com>
There was a problem hiding this comment.
♻️ Duplicate comments (1)
docs/stateless-migration-quickstart.md (1)
207-208: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winKeep target context naming consistent in validation examples.
Line 207-208 uses
tgt, but the command and JSON example use${TARGET_CONTEXT}/tgt-cluster. Please align these to one value throughout the section.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/stateless-migration-quickstart.md` around lines 207 - 208, The validation example uses inconsistent target context names, mixing “tgt” with “${TARGET_CONTEXT}” and “tgt-cluster” across the section. Update the affected example in the migration quickstart so the command output, JSON example, and any referenced context value all use the same target context name consistently. Use the surrounding validation example text and the “Mode: live (context: …)” output as the anchors when making the edit.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@docs/stateless-migration-quickstart.md`:
- Around line 207-208: The validation example uses inconsistent target context
names, mixing “tgt” with “${TARGET_CONTEXT}” and “tgt-cluster” across the
section. Update the affected example in the migration quickstart so the command
output, JSON example, and any referenced context value all use the same target
context name consistently. Use the surrounding validation example text and the
“Mode: live (context: …)” output as the anchors when making the edit.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9b44a759-5c88-4ff8-8082-e2e07ab11566
📒 Files selected for processing (1)
docs/stateless-migration-quickstart.md
Signed-off-by: M Sajid Mansoori <mmansoor@redhat.com>
Signed-off-by: M Sajid Mansoori <mmansoor@redhat.com>
istein1
approved these changes
Jun 26, 2026
Contributor
Author
|
/rfr |
midays
approved these changes
Jun 29, 2026
nachandr
reviewed
Jun 29, 2026
nachandr
approved these changes
Jun 30, 2026
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
4 participants
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.
Summary by CodeRabbit