Skip to content

feat(patterns): add rhoso-gitops pattern docs#694

Draft
cjeanner wants to merge 1 commit into
validatedpatterns:mainfrom
cjeanner:add-rhoso-gitops-pattern-docs
Draft

feat(patterns): add rhoso-gitops pattern docs#694
cjeanner wants to merge 1 commit into
validatedpatterns:mainfrom
cjeanner:add-rhoso-gitops-pattern-docs

Conversation

@cjeanner

Copy link
Copy Markdown

Add sandbox-tier documentation for the RHOSO GitOps pattern: overview, getting started, cluster sizing, configuration, and troubleshooting pages, reusable AsciiDoc modules, metadata from pattern-metadata.yaml, shared RHOSO attributes, and spellcheck wordlist entries.

Pattern repository links use cjeanner/pattern-rhoso-gitops for now. TODO(repo-move) comments mark github, bugs, and deploy URLs to update once the repo moves to validatedpatterns-sandbox/rhoso-gitops.

Architecture diagrams (GitOps delivery and infrastructure topology) were created on Miro and exported as SVG under static/images/rhoso-gitops/.

AI-Assist: Cursor; model=Composer; mode=agent; origin=cursor

Add sandbox-tier documentation for the RHOSO GitOps pattern:
overview, getting started, cluster sizing, configuration, and
troubleshooting pages, reusable AsciiDoc modules, metadata from
pattern-metadata.yaml, shared RHOSO attributes, and spellcheck
wordlist entries.

Pattern repository links use cjeanner/pattern-rhoso-gitops for now.
TODO(repo-move) comments mark github, bugs, and deploy URLs to update
once the repo moves to validatedpatterns-sandbox/rhoso-gitops.

Architecture diagrams (GitOps delivery and infrastructure topology)
were created on Miro and exported as SVG under static/images/rhoso-gitops/.

AI-Assist: Cursor; model=Composer; mode=agent; origin=cursor
@openshift-ci

openshift-ci Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

Hi @cjeanner. Thanks for your PR.

I'm waiting for a validatedpatterns member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant