Tuning log payloads and delivery section || Corrected tuning implementation YAML

[dhgautam99]

clf.spec.tuning doesn't exist in the product but the correct way of defining the tuning config is clf.spec.outputs.tuning

 $ oc explain clusterlogforwarder.spec.tuning
GROUP:      logging.openshift.io
KIND:       ClusterLogForwarder
VERSION:    v1error: field "tuning" does not exist

 $ oc explain clusterlogforwarder.spec.outputs.tuning
GROUP:      logging.openshift.io
KIND:       ClusterLogForwarder
VERSION:    v1FIELD: tuning <Object>DESCRIPTION:
    Tuning parameters for the output.  Specifying these parameters will alter
    the characteristics of log forwarder which may be different from its
    behavior without the tuning.

Same has been corrected in this PR.

Version(s): RHOCP 4.13, RHOCP 4.14 and RHOCP 4.15

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

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

[openshift-ci]

Hi @dhgautam99. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[libander]

Changes entirely to YAML.
/lgtm

[libander]

/ok-to-test

[libander]

@kabirbhartiRH / @anpingli - Review, please.

[ocpdocs-previewbot]

🤖 Fri Jun 14 19:54:04 - Prow CI generated the docs preview:

https://77521--ocpdocs-pr.netlify.app/openshift-dedicated/latest/observability/logging/log_collection_forwarding/configuring-log-forwarding.html
https://77521--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/log_collection_forwarding/configuring-log-forwarding.html
https://77521--ocpdocs-pr.netlify.app/openshift-rosa/latest/observability/logging/log_collection_forwarding/configuring-log-forwarding.html

[openshift-ci]

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

[libander]

@kabirbhartiRH / @anpingli - Review, please.

@dhgautam99 - the OCP repo won't accept a merge without QE review.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.