Fix logging documentation for eventrouter

[mburke5678]

Item #2 in https://bugzilla.redhat.com/show_bug.cgi?id=1758222#c0

2. The Deployment name should be "logging-eventrouter" instead of "cluster-logging-eventrouter" - the fluentd config expects the pod name to begin with "logging-eventrouter" - otherwise, the log records will not be assigned a UID matching the source UID of the event, they will be assigned a random UID

[openshift-docs-preview-bot]

The preview will be available shortly at:

• https://BZ-1758222--ocpdocs.netlify.com/

[mburke5678]

@richm Do all the instances of cluster-logging-eventrouter need to be changed to logging-eventrouter or just the deployment name?

[mburke5678]

@xltian Can you please assign this PR for review? Thank you!

[xltian]

@anpingli will review.

[anpingli]

LGTM

[mburke5678]

@richm PTAL

[richm]

The convention for 4.x is to remove the "logging-" prefix from names of objects in the cluster like pods, deployments, secrets, configmaps, etc. I have submitted a PR for logging to fix this: https://github.com/openshift/origin-aggregated-logging/pull/1766/files#diff-6bd9f2ef704c789f35e1652b8d6d5449

Note that image names will still have a "logging-" or "origin-logging-" or "ose-logging-" prefix.

[mburke5678]

@richm Thanks. I replaced the template in the docs with the one from your PR.

[richm]

/lgtm

[openshift-ci-robot]

New changes are detected. LGTM label has been removed.

[mburke5678]

/cherrypick enterprise-4.2

[openshift-cherrypick-robot]

@mburke5678: new pull request created: #17111

In response to this:

/cherrypick enterprise-4.2

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]

/cherrypick enterprise-4.1

[openshift-cherrypick-robot]

@mburke5678: new pull request created: #17112

In response to this:

/cherrypick enterprise-4.1

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.