Allow specification of a maximum line size to be applied after merging

[vparfonov]

Description

This PR adds the max_merged_line_bytes setting to the Vector collector configuration.
More information: kubernetes_logs/#max_merged_line_bytes

Currently, this parameter is not configurable via the Cluster Logging Forwarder spec and is hardcoded to 65536 bytes — which is twice the default value of max_line_bytes.

Using it helps prevent Vector from failing with the following error:
vector::topology: An error occurred that Vector couldn't handle: failed to encode record: BufferTooSmall.

/cc
/assign

Links

• Depending on PR(s):
• GitHub issue:
• JIRA: https://issues.redhat.com/browse/LOG-7347
• Enhancement proposal:

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vparfonov
Once this PR has been reviewed and has the lgtm label, please assign alanconway for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vparfonov]

/hold

[openshift-ci]

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