Skip to content

Conversation

@ochromy
Copy link

@ochromy ochromy commented Aug 12, 2025

Version(s):
enterprise-4.17

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

@openshift-ci openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 12, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Aug 13, 2025

🤖 Mon Sep 15 07:49:10 - Prow CI generated the docs preview:
https://97452--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

@ochromy ochromy force-pushed the OBSDOCS-1471 branch 6 times, most recently from 6e46c2b to 04e4c50 Compare August 18, 2025 06:50
@ochromy
Copy link
Author

ochromy commented Aug 25, 2025

/retest

@ochromy ochromy force-pushed the OBSDOCS-1471 branch 7 times, most recently from 4ce1d44 to 171df93 Compare August 28, 2025 11:22
Copy link
Contributor

@theashiot theashiot left a comment

Choose a reason for hiding this comment

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

Thanks, @ochromy for the wonderful work in this PR! I've added some suggestions inline. Apart from those suggestions, here are some more:

best,
ashwin

- Name: Viewing Logging status
File: cluster-logging-cluster-status
- Name: Troubleshooting log forwarding
File: log-forwarding-troubleshooting
Copy link
Contributor

Choose a reason for hiding this comment

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

Possibly missing the following:
- Name: Troubleshooting logging alerts
File: troubleshooting-logging-alerts
- Name: Viewing the status of the Elasticsearch log store
File: cluster-logging-log-store-status

Copy link

@anpingli anpingli Sep 18, 2025

Choose a reason for hiding this comment

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

can we create a separate panel for 5.8? And put all items(5.8 release note and etc) related to 5.8 under that link ?
Logging 6.2
Logging 6.1
Logging 6.0
Logging 5.8

image

resources:
limits:
memory: 32Gi
cpu: 200m
Copy link
Contributor

Choose a reason for hiding this comment

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

the changes in this file need technical review

@ochromy ochromy force-pushed the OBSDOCS-1471 branch 2 times, most recently from e57aa1f to c8b9073 Compare September 14, 2025 16:57
include assemblies

remove elasticsearch instances no1

fix topicmap no1

fix asciidoc no1

add loki-statement-snip

fix opentelemetry attributes

fix opentelemetry attributes no2

fix opentelemetry attributes no3

add logging 5.x from 4.16

topic-map fix no2

topic-map fix no3

topic-map fix no4

release note fix no1

kibana fix

topic_map fix no5

add release notes

add release notes no2

pr review no1 1/2

pr review no1 2/2

pr review no2

fix validation err no1
@openshift-ci
Copy link

openshift-ci bot commented Sep 15, 2025

@ochromy: all tests passed!

Full PR test history. Your PR dashboard.

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.

.Procedure

To use the Log Forward API to forward audit logs to the internal Elasticsearch instance:
To use the Log Forwarding API to forward audit logs to the internal Elasticsearch instance:

Choose a reason for hiding this comment

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

According to https://access.redhat.com/support/policy/updates/openshift_operators. Elasticsearch-opertaor in 4.16,4.17 is for trace only. I think we needn't remove all section as elasticsearch as interal store.

@anpingli
Copy link

anpingli commented Sep 18, 2025

According to https://access.redhat.com/support/policy/updates/openshift_operators. Elasticsearch-opertaor in 4.16,4.17 is for trace only. I think we needn't remove all sections as elasticsearch/kibana/curator.

+
[source,yaml]
----
$ oc edit ClusterLogging instance

Choose a reason for hiding this comment

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

This file is about elasticsearch, it can be removed.


. Change to the `openshift-logging` project:
+
[source,terminal]

Choose a reason for hiding this comment

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

This file is about elasticsearch, it can be removed.

[source,terminal]
----
$ oc adm must-gather --image=$(oc -n openshift-logging get deployment.apps/cluster-logging-operator -o jsonpath='{.spec.template.spec.containers[?(@.name == "cluster-logging-operator")].image}')
$ oc adm must-gather --image=quay.io/openshift/origin-cluster-logging-operator

Choose a reason for hiding this comment

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

Any reason we change the image to quay.io/openshift/origin-cluster-logging-operator?

@briandooley briandooley added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 20, 2025
@ochromy ochromy changed the title [OBSDOCS-1471] Logging 5.8 docs missing from 4.17 (ON HOLD) [OBSDOCS-1471] Logging 5.8 docs missing from 4.17 Oct 30, 2025
@briandooley
Copy link
Contributor

Closing as obsolete.

@briandooley briandooley closed this Dec 1, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 1, 2025
@openshift-merge-robot
Copy link

PR needs rebase.

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.

@briandooley
Copy link
Contributor

Closing as obsolete.

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

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants