Skip to content

Conversation

@mburke5678
Copy link
Contributor

Addding links to configuring page for each component and added log forwarding to the understanding cluster logging page.

@openshift-docs-preview-bot

The preview will be available shortly at:

@mburke5678
Copy link
Contributor Author

@sichvoge WDYT?

Copy link
Contributor

@bobfuru bobfuru left a comment

Choose a reason for hiding this comment

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

A few comments but otherwise LGTM!

Copy link
Contributor

Choose a reason for hiding this comment

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

"For more information, see..." (To avoid redundancy here?)
And same suggestion for the other xref additions here that are repeating the same wording.

Copy link
Contributor

Choose a reason for hiding this comment

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

s/see see/see/

Copy link
Contributor

Choose a reason for hiding this comment

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

I believe we are now using lowercase here ("Cluster Logging custom resource"), per the note that was updated in our guidelines:

You can use "object", "resource", "custom resource", "spec", etc. as appropriate after the object reference. This is especially recommended if it helps with clarity or readability.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@bobfuru
Agreed. I left it upper-case as it appears that way throughout the logging docs. I should do a universal change.

@bobfuru bobfuru added the peer-review-done Signifies that the peer review team has reviewed this PR label Nov 3, 2020
@mburke5678 mburke5678 force-pushed the logging-add-components branch from e2fdefd to 4ee9daa Compare November 3, 2020 20:06
@mburke5678 mburke5678 merged commit 079ad7a into openshift:master Nov 3, 2020
@mburke5678 mburke5678 deleted the logging-add-components branch November 3, 2020 21:14
@mburke5678
Copy link
Contributor Author

mburke5678 commented Nov 3, 2020

/cherrypick enterprise-4.5

@openshift-cherrypick-robot
Copy link

openshift-cherrypick-robot commented Nov 3, 2020

@mburke5678: new pull request created: #27025

Details

In response to this:

/cherrypick enterprise-4.5

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.

@mburke5678
Copy link
Contributor Author

mburke5678 commented Nov 3, 2020

/cherrypick enterprise-4.6

@openshift-cherrypick-robot
Copy link

openshift-cherrypick-robot commented Nov 3, 2020

@mburke5678: new pull request created: #27026

Details

In response to this:

/cherrypick enterprise-4.6

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.

@mburke5678
Copy link
Contributor Author

mburke5678 commented Dec 1, 2020

/cherrypick enterprise-4.7

@openshift-cherrypick-robot
Copy link

openshift-cherrypick-robot commented Dec 1, 2020

@mburke5678: new pull request created: #27747

Details

In response to this:

/cherrypick enterprise-4.7

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.

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

Labels

branch/enterprise-4.5 branch/enterprise-4.6 branch/enterprise-4.7 peer-review-done Signifies that the peer review team has reviewed this PR size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants