[release-5.8]LOG-4671:respect settings containerLimit.maxRecordsPerSecond to 0

[vparfonov]

Description

/cc @cahartma @Clee2691
/assign @jcantrill

/cherry-pick

Links

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

[openshift-ci-robot]

@vparfonov: This pull request references LOG-4671 which is a valid jira issue.

In response to this:

Description

/cc @cahartma @Clee2691
/assign @jcantrill

/cherry-pick

Links

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

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 openshift-eng/jira-lifecycle-plugin repository.

[vparfonov]

/retest

[jcantrill]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, vparfonov

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jcantrill]

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

[jcantrill]

@vparfonov You will need to clone this issue and port it forward to 6.0 and maybe 5.9 thought 5.9 I believe is going EOL shortly so maybe hold off for the time being

[vparfonov]

/cherry-pick release-5.9

[openshift-cherrypick-robot]

@vparfonov: once the present PR merges, I will cherry-pick it on top of release-5.9 in a new PR and assign it to you.

In response to this:

/cherry-pick release-5.9

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.

[vparfonov]

/test e2e-target

[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.

[openshift-cherrypick-robot]

@vparfonov: #2802 failed to apply on top of branch "release-5.9":

Applying: LOG-4671:respect settings containerLimit.maxRecordsPerSecond to 0
.git/rebase-apply/patch:134: space before tab in indent.
  	}
.git/rebase-apply/patch:152: space before tab in indent.
  		. = compact(., nullish: true)
.git/rebase-apply/patch:190: space before tab in indent.
  	.level = "trace"
.git/rebase-apply/patch:192: space before tab in indent.
  	priority = to_int!(.PRIORITY)
.git/rebase-apply/patch:193: space before tab in indent.
  	.level, err = to_syslog_level(priority)
warning: squelched 7 whitespace errors
warning: 12 lines add whitespace errors.
Using index info to reconstruct a base tree...
A	internal/generator/vector/conf_test.go
A	internal/generator/vector/inputs.go
A	internal/generator/vector/pipelines.go
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): internal/generator/vector/pipelines.go deleted in HEAD and modified in LOG-4671:respect settings containerLimit.maxRecordsPerSecond to 0. Version LOG-4671:respect settings containerLimit.maxRecordsPerSecond to 0 of internal/generator/vector/pipelines.go left in tree.
CONFLICT (modify/delete): internal/generator/vector/inputs.go deleted in HEAD and modified in LOG-4671:respect settings containerLimit.maxRecordsPerSecond to 0. Version LOG-4671:respect settings containerLimit.maxRecordsPerSecond to 0 of internal/generator/vector/inputs.go left in tree.
Auto-merging internal/generator/vector/conf/conf_test.go
CONFLICT (content): Merge conflict in internal/generator/vector/conf/conf_test.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 LOG-4671:respect settings containerLimit.maxRecordsPerSecond to 0

In response to this:

/cherry-pick release-5.9

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.

[openshift-cherrypick-robot]

@vparfonov: cannot checkout <!--: error checking out "<!--": exit status 1 error: pathspec '<!--' did not match any file(s) known to git

In response to this:

Description

/cc @cahartma @Clee2691
/assign @jcantrill

/cherry-pick

Links

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

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.