Add several request/response headers in audit log entries

[vrutkovs]

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[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-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 14b05bd|Store "openshift.io/request-header-accept", "openshift.io/request-header-accept-encoding" and "openshift.io/request-header-content-length": does not specify an upstream backport in the commit message
• 3cc01e2|Store "openshift.io/request-header-host" annotation in audit logs: does not specify an upstream backport in the commit message
• 71fd64a|audit: store accept/accept-encoding/content-length audit log annotations: does not specify an upstream backport in the commit message
• ac75c81|HACK: fix request Host storing in openshift.io/during-graceful audit log annotation: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vrutkovs
Once this PR has been reviewed and has the lgtm label, please assign tkashem for approval. For more information see the Kubernetes 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:

• DOWNSTREAM_OWNERS

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

[vrutkovs]

/test e2e-aws-ovn-serial

[vrutkovs]

/payload-job-with-prs openshift/origin#29222 periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

[openshift-ci]

@vrutkovs: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial openshift/origin#29222

[openshift-ci]

@vrutkovs: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial https://github.com/openshift/origin/pull/29222,openshift/kubernetes#2121,openshift/cluster-monitoring-operator#2505

[openshift-ci]

@vrutkovs: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial openshift/origin/pull/29222 #2121 openshift/cluster-monitoring-operator#2505

[openshift-ci]

@vrutkovs: An error was encountered. No known errors were detected, please see the full error message for details.

Full error message.

unable to get additional pr info from string: openshift/origin/pull/29222: string: openshift/origin/pull/29222 doesn't match expected format: org/repo#number

Please contact an administrator to resolve this issue.

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial https://github.com/openshift/origin#29222 #2121 openshift/cluster-monitoring-operator#2505

[openshift-ci]

@vrutkovs: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial openshift/origin#29222 #2121 openshift/cluster-monitoring-operator#2505

[openshift-ci]

@vrutkovs: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8ead4490-9117-11ef-8662-fdd14cd693cb-0

[openshift-ci]

@vrutkovs: This PR was included in a payload test run from #2121
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8ead4490-9117-11ef-8662-fdd14cd693cb-0

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial https://github.com/openshift/origin#29222 https://github.com/openshift/kubernetes#2121 https://github.com/openshift/cluster-monitoring-operator#2505 cluster-csi-snapshot-controller-operator#217 machine-config-operator#4658

[openshift-ci]

@vrutkovs: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial openshift/origin#29222 #2121 openshift/cluster-monitoring-operator#2505 openshift/cluster-csi-snapshot-controller-operator#217 openshift/machine-config-operator#4658

[openshift-ci]

@vrutkovs: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/17dde510-911a-11ef-90f7-2ad72545de28-0

[openshift-ci]

@vrutkovs: This PR was included in a payload test run from #2121
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/17dde510-911a-11ef-90f7-2ad72545de28-0

[openshift-ci]

@vrutkovs: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9f7b0780-91d0-11ef-801e-f8298112fd81-0

[openshift-ci]

@vrutkovs: This PR was included in a payload test run from #2121
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9f7b0780-91d0-11ef-801e-f8298112fd81-0

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 14b05bd|Store "openshift.io/request-header-accept", "openshift.io/request-header-accept-encoding" and "openshift.io/request-header-content-length": does not specify an upstream backport in the commit message
• 26df186|scheduler: use protobuf: does not specify an upstream backport in the commit message
• 3cc01e2|Store "openshift.io/request-header-host" annotation in audit logs: does not specify an upstream backport in the commit message
• 4c6f6cc|audit: store accept/accept-encoding/content-length audit log annotations: does not specify an upstream backport in the commit message
• 762f3eb|HACK: store all response headers: does not specify an upstream backport in the commit message
• ac75c81|HACK: fix request Host storing in openshift.io/during-graceful audit log annotation: does not specify an upstream backport in the commit message
• d62988f|controller-manager: namespace-controller should use protobuf: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[vrutkovs]

/test e2e-aws-ovn-serial

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 14b05bd|Store "openshift.io/request-header-accept", "openshift.io/request-header-accept-encoding" and "openshift.io/request-header-content-length": does not specify an upstream backport in the commit message
• 26df186|scheduler: use protobuf: does not specify an upstream backport in the commit message
• 3cc01e2|Store "openshift.io/request-header-host" annotation in audit logs: does not specify an upstream backport in the commit message
• 4c6f6cc|audit: store accept/accept-encoding/content-length audit log annotations: does not specify an upstream backport in the commit message
• a56a987|HACK: store all response headers: does not specify an upstream backport in the commit message
• ac75c81|HACK: fix request Host storing in openshift.io/during-graceful audit log annotation: does not specify an upstream backport in the commit message
• d62988f|controller-manager: namespace-controller should use protobuf: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 14b05bd|Store "openshift.io/request-header-accept", "openshift.io/request-header-accept-encoding" and "openshift.io/request-header-content-length": does not specify an upstream backport in the commit message
• 1cf4aa6|HACK: store all response headers: does not specify an upstream backport in the commit message
• 26df186|scheduler: use protobuf: does not specify an upstream backport in the commit message
• 3cc01e2|Store "openshift.io/request-header-host" annotation in audit logs: does not specify an upstream backport in the commit message
• 4c6f6cc|audit: store accept/accept-encoding/content-length audit log annotations: does not specify an upstream backport in the commit message
• ac75c81|HACK: fix request Host storing in openshift.io/during-graceful audit log annotation: does not specify an upstream backport in the commit message
• d62988f|controller-manager: namespace-controller should use protobuf: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[vrutkovs]

/test e2e-aws-ovn-serial

[openshift-ci]

@vrutkovs: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-serial	1cf4aa6	link	true	/test e2e-aws-ovn-serial

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.

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial openshift/origin#29222 #2121 openshift/cluster-monitoring-operator#2505 cluster-csi-snapshot-controller-operator#217 openshift/machine-config-operator#4658

[openshift-ci]

@vrutkovs: An error was encountered. No known errors were detected, please see the full error message for details.

Full error message.

unable to get additional pr info from string: cluster-csi-snapshot-controller-operator#217: string: cluster-csi-snapshot-controller-operator#217 doesn't match expected format: org/repo#number

Please contact an administrator to resolve this issue.

[openshift-ci-robot]

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 14b05bd|Store "openshift.io/request-header-accept", "openshift.io/request-header-accept-encoding" and "openshift.io/request-header-content-length": does not specify an upstream backport in the commit message
• 26df186|scheduler: use protobuf: does not specify an upstream backport in the commit message
• 3cc01e2|Store "openshift.io/request-header-host" annotation in audit logs: does not specify an upstream backport in the commit message
• 4c6f6cc|audit: store accept/accept-encoding/content-length audit log annotations: does not specify an upstream backport in the commit message
• ac75c81|HACK: fix request Host storing in openshift.io/during-graceful audit log annotation: does not specify an upstream backport in the commit message
• d62988f|controller-manager: namespace-controller should use protobuf: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial openshift/origin#29222 #2121 openshift/cluster-monitoring-operator#2505 openshift/cluster-csi-snapshot-controller-operator#217 openshift/machine-config-operator#4658 openshift/cluster-etcd-operator#1361

[openshift-ci]

@vrutkovs: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b4572c50-92c1-11ef-9dc8-8ee5ecca121f-0

[openshift-ci]

@vrutkovs: This PR was included in a payload test run from #2121
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b4572c50-92c1-11ef-9dc8-8ee5ecca121f-0

[vrutkovs]

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial openshift/origin#29222 #2121 openshift/cluster-monitoring-operator#2505 openshift/cluster-csi-snapshot-controller-operator#217 openshift/machine-config-operator#4658 openshift/cluster-etcd-operator#1361

[openshift-ci]

@vrutkovs: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/31391bc0-92ef-11ef-8a0e-563ed35e32a0-0

[openshift-ci]

@vrutkovs: This PR was included in a payload test run from #2121
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/31391bc0-92ef-11ef-8a0e-563ed35e32a0-0

[openshift-ci]

@vrutkovs: This PR was included in a payload test run from #2124
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fd0725a0-960d-11ef-9b20-c6c69022f342-0

[openshift-ci]

@vrutkovs: This PR was included in a payload test run from #2124
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/081fe680-96da-11ef-91f4-cde4735e474b-0

[openshift-ci]

@vrutkovs: This PR was included in a payload test run from #2124
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a7c78740-96f5-11ef-8917-56e896fcf5d0-0

[openshift-ci]

@vrutkovs: This PR was included in a payload test run from #2124
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/20169390-9790-11ef-9369-5b6a6b14fab2-0