-
Notifications
You must be signed in to change notification settings - Fork 1.9k
adding log forwarding and links to Understanding cluster logging #26899
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.
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
Conversation
|
The preview will be available shortly at: |
|
@sichvoge WDYT? |
433d907 to
e2fdefd
Compare
bobfuru
left a comment
There was a problem hiding this 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!
logging/cluster-logging.adoc
Outdated
There was a problem hiding this comment.
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.
logging/cluster-logging.adoc
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/see see/see/
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
e2fdefd to
4ee9daa
Compare
|
/cherrypick enterprise-4.5 |
|
@mburke5678: new pull request created: #27025 DetailsIn response to this:
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. |
|
/cherrypick enterprise-4.6 |
|
@mburke5678: new pull request created: #27026 DetailsIn response to this:
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. |
|
/cherrypick enterprise-4.7 |
|
@mburke5678: new pull request created: #27747 DetailsIn response to this:
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. |
Addding links to configuring page for each component and added log forwarding to the understanding cluster logging page.