Skip to content

[enterprise-4.16] OBSDOCS-2209: Place a redirect notice on OCP logging docs #96640

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 4, 2025
Merged

[enterprise-4.16] OBSDOCS-2209: Place a redirect notice on OCP logging docs #96640

merged 1 commit into from
Aug 4, 2025

Conversation

theashiot
Copy link
Contributor

@theashiot theashiot commented Jul 24, 2025 •
edited
Loading

Version(s): 4.16

Issue: https://issues.redhat.com/browse/OBSDOCS-2209

QE review: Not required as there are not technical changes.
Additional information:

Original PR to main: #94807

All the following PRs are for making the change in the original PR to older releases. I had to make separate PRs because the structure of the logging docs is different in each older release and therefore automatic cherry-picks would have failed. Please consider reviewing the following PRs as well:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 24, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 24, 2025 •
edited by openshift-ci bot
Loading

@theashiot: This pull request references OBSDOCS-2209 which is a valid jira issue.

In response to this:

Version(s): 4.16

Issue: https://issues.redhat.com/browse/OBSDOCS-2209

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 Jul 24, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jul 24, 2025 •
edited
Loading

🤖 Mon Jul 28 10:59:25 - Prow CI generated the docs preview:

https://96640--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.0/log6x-about-logging.html
https://96640--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.1/log6x-about-logging.html
https://96640--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.2/log6x-about-logging.html
https://96640--ocpdocs-pr.netlify.app/openshift-enterprise/latest/scalability_and_performance/telco_ref_design_specs/ran/telco-ran-ref-du-components.html

@theashiot theashiot force-pushed the OBSDOCS-2209-4.16 branch from 3dffef1 to 9d0794c Compare July 24, 2025 13:02
@theashiot theashiot force-pushed the OBSDOCS-2209-4.16 branch from 9d0794c to 45f9b7c Compare July 28, 2025 10:22
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jul 28, 2025

@theashiot: 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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 28, 2025 •
edited by openshift-ci bot
Loading

@theashiot: This pull request references OBSDOCS-2209 which is a valid jira issue.

In response to this:

Version(s): 4.16

Issue: https://issues.redhat.com/browse/OBSDOCS-2209

QE review: Not required as there are not technical changes.
Additional information:

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.

This was referenced Jul 28, 2025
Merged
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 28, 2025 •
edited by openshift-ci bot
Loading

@theashiot: This pull request references OBSDOCS-2209 which is a valid jira issue.

In response to this:

Version(s): 4.16

Issue: https://issues.redhat.com/browse/OBSDOCS-2209

QE review: Not required as there are not technical changes.
Additional information:

Original PR to main: #94807

All the following PRs are for making the change in the original PR to older releases. I had to make separate PRs because the structure of the logging docs is different in each older release and therefore automatic cherry-picks would have failed. Please consider reviewing the following PRs as well:

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.

max-cx
max-cx reviewed Jul 30, 2025
View reviewed changes
Copy link
Contributor

@max-cx max-cx left a comment

Choose a reason for hiding this comment

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

Peer review done.

Just one comment below here. Please also see my comments in #96624 (review).

@max-cx max-cx changed the title OBSDOCS-2209: [4.16] Place a redirect notice on OCP logging docs [enterprise-4.16] OBSDOCS-2209: Place a redirect notice on OCP logging docs Aug 4, 2025
@max-cx max-cx merged commit 8c4f849 into openshift:enterprise-4.16 Aug 4, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@max-cx max-cx max-cx left review comments

Assignees
No one assigned
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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@theashiot @openshift-ci-robot @ocpdocs-previewbot @max-cx