Skip to content

docs: Simplify RHCL disconnected installation to follow Red Hat patterns#2

Draft
mikenairn wants to merge 2 commits into
ShaunaDiaz:OSDOCS-19851from
mikenairn:OSDOCS-19851-suggestions
Draft

docs: Simplify RHCL disconnected installation to follow Red Hat patterns#2
mikenairn wants to merge 2 commits into
ShaunaDiaz:OSDOCS-19851from
mikenairn:OSDOCS-19851-suggestions

Conversation

@mikenairn

Copy link
Copy Markdown

Problem: Current RHCL disconnected docs use upstream catalog (quay.io/kuadrant), wrong package name (kuadrant-operator), and single-step mirroring that doesn't work for true air-gapped environments.

Solution: Simplified docs that:

  1. Use Red Hat catalog with correct package name (rhcl-operator)
  2. Show two-step mirroring (mirror to disk → transfer → push to registry)
  3. Focus on RHCL-specific details only, reference existing OLM disconnected docs for generic setup
  4. Remove troubleshooting modules with wrong package names

Pattern: Matches how other Red Hat operators document disconnected installation (HCP, MCE, Loki).

Critical fixes:

  • Package name: kuadrant-operator → rhcl-operator
  • Catalog: quay.io/kuadrant/... → registry.redhat.io/redhat/redhat-operator-index
  • Mirroring: Single-step → Two-step disk-based workflow
  • CoreDNS image: quay.io/kuadrant/... → registry.redhat.io/rhcl-1/coredns-rhel9

NOTE: You do not need to merge this(it was generated), but it was the easiest way i could see to show the correct procedures and names of items needed.

ShaunaDiaz and others added 2 commits June 2, 2026 14:41
Problem: Current RHCL disconnected docs use upstream catalog (quay.io/kuadrant),
wrong package name (kuadrant-operator), and single-step mirroring that doesn't
work for true air-gapped environments.

Solution: Simplified docs that:
1. Use Red Hat catalog with correct package name (rhcl-operator)
2. Show two-step mirroring (mirror to disk → transfer → push to registry)
3. Focus on RHCL-specific details only, reference existing OLM disconnected
   docs for generic setup
4. Remove troubleshooting modules with wrong package names

Pattern: Matches how other Red Hat operators document disconnected installation
(HCP, MCE, Loki).

Critical fixes:
- Package name: kuadrant-operator → rhcl-operator
- Catalog: quay.io/kuadrant/... → registry.redhat.io/redhat/redhat-operator-index
- Mirroring: Single-step → Two-step disk-based workflow
- CoreDNS image: quay.io/kuadrant/... → registry.redhat.io/rhcl-1/coredns-rhel9

Signed-off-by: Michael Nairn <mnairn@redhat.com>

.Prerequisites

* A disconnected {ocp} cluster version 4.14 or later

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

RHCL 1.4.0 doesn't support this version of OCP AFIAK (prereqs do not go in assemblies, either; we have these in the modules)


[role="_abstract"]
By using {prodname} as disconnected gateway, you can securely route traffic, enforce rate limits, and perform automated failover between your isolated clusters. You can also automate internal TLS certificate management and manage all internal networking and security policies.
{prodname} provides policy-driven traffic management for {ocp} clusters using Gateway API. In a disconnected environment, you must mirror the {prodname} operator catalog and its container images to your local registry before installation.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

we need to retain the user-focus and not talk about features, but use

= About installing {prodname} in disconnected environments

[role="_abstract"]
By using {prodname} as disconnected gateway, you can securely route traffic, enforce rate limits, and perform automated failover between your isolated clusters. You can also automate internal TLS certificate management and manage all internal networking and security policies.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

is this text wrong as far as what a user can do?

//
// *install-guide/disconnected-install.adoc

:_mod-docs-content-type: PROCEDURE

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

most of this is in the existing documentation; i do see some differences in the YAMLs, but they are small--can we use what we have with notes for disconnected?

metadata:
name: kuadrant-operator-group
namespace: kuadrant-system
spec: {}

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

regular install doc has:

kind: OperatorGroup
apiVersion: operators.coreos.com/v1
metadata:
name: kuadrant
namespace: <kuadrant_system>
spec:
upgradeStrategy: Default

could we just say to leave the spec empty for disconnected?

@ShaunaDiaz ShaunaDiaz force-pushed the OSDOCS-19851 branch 13 times, most recently from 74f72f9 to 3804c3e Compare June 9, 2026 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants