Skip to content

OBSDOCS-3551, OBSDOCS-3552, OBSDOCS-3553: Fix installation documentation issues#114284

Open
johnwilkins wants to merge 2 commits into
openshift:standalone-logging-docs-mainfrom
johnwilkins:OBSDOCS-3551
Open

OBSDOCS-3551, OBSDOCS-3552, OBSDOCS-3553: Fix installation documentation issues#114284
johnwilkins wants to merge 2 commits into
openshift:standalone-logging-docs-mainfrom
johnwilkins:OBSDOCS-3551

Conversation

@johnwilkins

@johnwilkins johnwilkins commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes three related installation documentation bugs by improving clarity, accuracy, and organization of the installation guides.

Changes

OBSDOCS-3551: Installation guide improvements

  • Added COO to installation workflow steps
  • Made log forwarding destination lists generic (removed closed lists like "Splunk, Elasticsearch, or cloud logging")
  • Fixed incorrect oc CLI reference to logcli for LogQL queries
  • Scoped preinstallation checklist to LokiStack deployments only (added note for log-forwarding-only scenarios)
  • Aligned deployment scenarios sizing with volume-based approach (compatible with pending PR OBSDOCS-3530: Add per-component LokiStack resource tables for capacity planning #114090)
  • Removed incorrect storage backend assumptions tied to deployment type
  • Added important warning about multi-cluster LokiStack limitation (cannot aggregate logs from multiple clusters)

OBSDOCS-3552: Namespace creation documentation

  • Added complete namespace YAML with required openshift.io/cluster-monitoring: "true" label
  • Included proper annotations for node selector
  • Moved namespace creation from prerequisites to procedure steps in CLI installation

OBSDOCS-3553: Installation step consistency

  • Reorganized CLO installation assembly with clear section headers:
    • "Installing the Operator" (CLI or Console)
    • "Configuring log collection" (shared steps)
    • "Optional: Additional configuration"
    • "Verification and troubleshooting"
  • Moved COO installation to prerequisites with xref (no longer duplicated)
  • Added LokiStack prerequisite to ClusterLogForwarder creation
  • Created new troubleshooting module for Loki Operator and moved Loki-specific troubleshooting there

JIRA Tickets

Compatibility

All changes are compatible with pending Loki sizing PR #114090. Issue 6 from OBSDOCS-3551 (incorrect sizing recommendations) is already addressed by that PR.

Files Modified

  • installing/installing-the-loki-operator.adoc
  • installing/installing-the-red-hat-openshift-logging-operator.adoc
  • modules/creating-the-clusterlogforwarder.adoc
  • modules/enabling-the-logs-tab.adoc
  • modules/installing-the-clo-cli.adoc
  • modules/logging-deployment-scenarios.adoc
  • modules/logging-installation-workflow.adoc
  • modules/logging-operator-requirements.adoc
  • modules/logging-preinstallation-checklist.adoc
  • modules/troubleshooting-logging-installation.adoc

Files Created

  • modules/troubleshooting-loki-operator-installation.adoc

Signed-off-by: John Wilkins jowilkin@redhat.com

…ion issues

This commit addresses multiple installation documentation issues:

OBSDOCS-3551: Installation guide improvements
- Add COO requirement to installation workflow
- Make log forwarding destination lists generic instead of closed
- Fix incorrect oc CLI reference (changed to logcli)
- Scope preinstallation checklist to LokiStack deployments only
- Align deployment scenarios with volume-based sizing (compatible with PR openshift#114090)
- Add multi-cluster LokiStack limitation warning

OBSDOCS-3552: Add namespace creation documentation
- Add complete namespace YAML with required monitoring labels/annotations
- Include instructions for creating openshift-logging namespace in CLI installation

OBSDOCS-3553: Fix inconsistent installation steps
- Reorganize CLO installation assembly with clear CLI/Console sections
- Move COO installation to prerequisites instead of duplicating
- Add LokiStack prerequisite to ClusterLogForwarder creation
- Move Loki Operator troubleshooting to Loki Operator installation guide

Related:
- https://redhat.atlassian.net/browse/OBSDOCS-3551
- https://redhat.atlassian.net/browse/OBSDOCS-3552
- https://redhat.atlassian.net/browse/OBSDOCS-3553

Signed-off-by: John Wilkins <jowilkin@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 29, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 29, 2026

Copy link
Copy Markdown

@johnwilkins: This pull request references OBSDOCS-3551 which is a valid jira issue.

This pull request references OBSDOCS-3552 which is a valid jira issue.

This pull request references OBSDOCS-3553 which is a valid jira issue.

Details

In response to this:

Summary

Fixes three related installation documentation bugs by improving clarity, accuracy, and organization of the installation guides.

Changes

OBSDOCS-3551: Installation guide improvements

  • Added COO to installation workflow steps
  • Made log forwarding destination lists generic (removed closed lists like "Splunk, Elasticsearch, or cloud logging")
  • Fixed incorrect oc CLI reference to logcli for LogQL queries
  • Scoped preinstallation checklist to LokiStack deployments only (added note for log-forwarding-only scenarios)
  • Aligned deployment scenarios sizing with volume-based approach (compatible with pending PR OBSDOCS-3530: Add per-component LokiStack resource tables for capacity planning #114090)
  • Removed incorrect storage backend assumptions tied to deployment type
  • Added important warning about multi-cluster LokiStack limitation (cannot aggregate logs from multiple clusters)

OBSDOCS-3552: Namespace creation documentation

  • Added complete namespace YAML with required openshift.io/cluster-monitoring: "true" label
  • Included proper annotations for node selector
  • Moved namespace creation from prerequisites to procedure steps in CLI installation

OBSDOCS-3553: Installation step consistency

  • Reorganized CLO installation assembly with clear section headers:
  • "Installing the Operator" (CLI or Console)
  • "Configuring log collection" (shared steps)
  • "Optional: Additional configuration"
  • "Verification and troubleshooting"
  • Moved COO installation to prerequisites with xref (no longer duplicated)
  • Added LokiStack prerequisite to ClusterLogForwarder creation
  • Created new troubleshooting module for Loki Operator and moved Loki-specific troubleshooting there

JIRA Tickets

Compatibility

All changes are compatible with pending Loki sizing PR #114090. Issue 6 from OBSDOCS-3551 (incorrect sizing recommendations) is already addressed by that PR.

Files Modified

  • installing/installing-the-loki-operator.adoc
  • installing/installing-the-red-hat-openshift-logging-operator.adoc
  • modules/creating-the-clusterlogforwarder.adoc
  • modules/enabling-the-logs-tab.adoc
  • modules/installing-the-clo-cli.adoc
  • modules/logging-deployment-scenarios.adoc
  • modules/logging-installation-workflow.adoc
  • modules/logging-operator-requirements.adoc
  • modules/logging-preinstallation-checklist.adoc
  • modules/troubleshooting-logging-installation.adoc

Files Created

  • modules/troubleshooting-loki-operator-installation.adoc

Signed-off-by: John Wilkins jowilkin@redhat.com

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 29, 2026
The previous xref pointed to ../log_forwarding/log-forwarding.adoc which
doesn't exist in the openshift-logging distro. The correct path is
../configuring/configuring-log-forwarding.adoc.

This fixes the portal build validation error.

Signed-off-by: John Wilkins <jowilkin@redhat.com>
include::modules/creating-the-clusterlogforwarder.adoc[leveloffset=+2]

[id="optional-configuration_{context}"]
== Optional: Additional configuration

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] OpenShiftAsciiDoc.NoOptionalTitles: Do not begin a module or assembly title with 'Optional:'.

@openshift-ci

openshift-ci Bot commented Jun 29, 2026

Copy link
Copy Markdown

@johnwilkins: all tests passed!

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.

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

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants