Skip to content

clearer instruction to disable default argocd instance - #412

Open
makeittotop wants to merge 1 commit into
redhat-developer:masterfrom
makeittotop:patch-1
Open

clearer instruction to disable default argocd instance#412
makeittotop wants to merge 1 commit into
redhat-developer:masterfrom
makeittotop:patch-1

Conversation

@makeittotop

Copy link
Copy Markdown

What type of PR is this?
/kind documentation

What does this PR do / why we need it:
Specifically mentioning to edit the env resource within the subscriptions.operators.coreos.com.spec.config CRD to add the associated env. var. in order to disable the default argocd instance launch.

Have you updated the necessary documentation?

  • Documentation update is required by this PR.
  • Documentation has been updated.

Which issue(s) this PR fixes:

Fixes #?

Test acceptance criteria:

  • Unit Test
  • E2E Test

How to test changes / Special notes to the reviewer:

@openshift-ci openshift-ci Bot added the kind/documentation Improvements or additions to documentation label Dec 7, 2022
@openshift-ci
openshift-ci Bot requested review from chetan-rns and jgwest December 7, 2022 12:18
@openshift-ci

openshift-ci Bot commented Dec 7, 2022

Copy link
Copy Markdown

Hi @makeittotop. Thanks for your PR.

I'm waiting for a redhat-developer 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/test-infra repository.

@iam-veeramalla

Copy link
Copy Markdown
Contributor

ok-to-test

@varshab1210

Copy link
Copy Markdown
Member

/retest

@saumeya

saumeya commented Sep 4, 2024

Copy link
Copy Markdown
Member

@makeittotop I know it is an old PR but can you rebase this ?

@makeittotop

makeittotop commented Sep 8, 2024 via email

Copy link
Copy Markdown
Author

@openshift-ci

openshift-ci Bot commented Jan 16, 2025

Copy link
Copy Markdown

@makeittotop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/v4.8-kuttl-sequential ebfc639 link true /test v4.8-kuttl-sequential
ci/prow/v4.8-kuttl-parallel ebfc639 link true /test v4.8-kuttl-parallel
ci/prow/v4.9-kuttl-sequential ebfc639 link true /test v4.9-kuttl-sequential
ci/prow/v4.12-kuttl-parallel ebfc639 link true /test v4.12-kuttl-parallel
ci/prow/v4.12-kuttl-sequential ebfc639 link true /test v4.12-kuttl-sequential
ci/prow/v4.10-kuttl-parallel ebfc639 link true /test v4.10-kuttl-parallel
ci/prow/v4.10-kuttl-sequential ebfc639 link true /test v4.10-kuttl-sequential
ci/prow/v4.11-kuttl-sequential ebfc639 link true /test v4.11-kuttl-sequential
ci/prow/v4.13-kuttl-sequential ebfc639 link true /test v4.13-kuttl-sequential
ci/prow/v4.13-kuttl-parallel ebfc639 link true /test v4.13-kuttl-parallel
ci/prow/v4.13-e2e ebfc639 link true /test v4.13-e2e
ci/prow/v4.14-kuttl-sequential-periodic ebfc639 link true /test v4.14-kuttl-sequential-periodic
ci/prow/v4.14-kuttl-sequential ebfc639 link true /test v4.14-kuttl-sequential
ci/prow/v4.14-kuttl-parallel ebfc639 link true /test v4.14-kuttl-parallel

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@olivergondza

Copy link
Copy Markdown
Collaborator

/approve
/lgtm

@openshift-ci

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: olivergondza

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:

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

Clearly mentioning the `env` resource within the `subscriptions.operators.coreos.com.spec.config` CRD to add the associated env. var. leading to disabling the default argocd  instance launch
@openshift-ci

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Updated the ROSA/OSD installation guide with step-by-step instructions for disabling the default Argo CD installation.
    • Added a concrete Subscription YAML example showing the required configuration.

Walkthrough

The ROSA/OSD installation guidance now explains how to disable the default Argo CD instance through the GitOps Operator Subscription, including a concrete YAML example.

Changes

OpenShift GitOps documentation

Layer / File(s) Summary
Document Subscription configuration
docs/OpenShift GitOps Usage Guide.md
Installation instructions now specify spec.config.env and show DISABLE_DEFAULT_ARGOCD_INSTANCE set to "TRUE".

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

Suggested reviewers: jgwest, chetan-rns

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly reflects the main change: clarifying how to disable the default Argo CD instance.
Description check ✅ Passed The description is directly related to the documentation update and explains the env var change in the GitOps Subscription.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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.

❤️ Share

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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/OpenShift` GitOps Usage Guide.md:
- Line 124: Update the fenced code block in the OpenShift GitOps Usage Guide to
use a yaml language identifier, changing the opening fence to ```yaml while
preserving the block contents and closing fence.
- Around line 125-130: Correct the Subscription YAML example by adding the
missing metadata mapping before name and namespace, keeping those fields nested
under metadata and preserving kind as its own top-level field.
🪄 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: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c6dd3706-80ab-4f0c-9145-2b05a76abd0f

📥 Commits

Reviewing files that changed from the base of the PR and between 804bf2a and e6a680d.

📒 Files selected for processing (1)
  • docs/OpenShift GitOps Usage Guide.md
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • argoproj-labs/argocd-operator (manual)

To disable the default ‘ready-to-use’ installation of Argo CD: as an admin, update the existing Subscription Object for Gitops Operator and add `DISABLE_DEFAULT_ARGOCD_INSTANCE = true` to the spec.
To disable the default ‘ready-to-use’ installation of Argo CD: as an admin, update the existing Subscription Object for Gitops Operator and add `DISABLE_DEFAULT_ARGOCD_INSTANCE = true` to the `subscriptions.operators.coreos.com.spec.config.env` resource as follows -

```

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Declare the fenced block as YAML.

Use ```yaml instead of an untyped fence to satisfy markdownlint MD040 and provide correct syntax highlighting.

🧰 Tools
🪛 markdownlint-cli2 (0.23.1)

[warning] 124-124: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 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/OpenShift` GitOps Usage Guide.md at line 124, Update the fenced code
block in the OpenShift GitOps Usage Guide to use a yaml language identifier,
changing the opening fence to ```yaml while preserving the block contents and
closing fence.

Source: Linters/SAST tools

Comment on lines +125 to +130
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
name: openshift-gitops-operator
namespace: openshift-operators
spec:
config:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Add the missing metadata: key to the Subscription example.

name and namespace are currently indented beneath the scalar kind field, so this block is invalid YAML and cannot be applied.

Proposed fix
 apiVersion: operators.coreos.com/v1alpha1
 kind: Subscription
+metadata:
   name: openshift-gitops-operator
   namespace: openshift-operators
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
name: openshift-gitops-operator
namespace: openshift-operators
spec:
config:
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: openshift-gitops-operator
namespace: openshift-operators
spec:
config:
🤖 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/OpenShift` GitOps Usage Guide.md around lines 125 - 130, Correct the
Subscription YAML example by adding the missing metadata mapping before name and
namespace, keeping those fields nested under metadata and preserving kind as its
own top-level field.

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

Labels

approved kind/documentation Improvements or additions to documentation ok-to-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants