Use protobuf for core clients

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

• 3f64cd2|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
• 466d1c7|Use protobuf for core clients: does not specify an upstream backport in the commit message
• 4a17246|audit: store accept/accept-encoding/content-length audit log annotations: does not specify an upstream backport in the commit message
• 781b092|UPSTREAM: : Add OpenShift tooling, images, configs and docs: does not specify an upstream backport in the commit message
• 8979f1d|client-go/rest: move content type wiring from client to request: does not specify an upstream backport in the commit message
• d26684b|Store "openshift.io/request-header-host" annotation in audit logs: does not specify an upstream backport in the commit message
• db61bcf|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 bertinatto 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

[openshift-ci]

@vrutkovs: 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-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:

• 3f64cd2|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
• 466d1c7|Use protobuf for core clients: does not specify an upstream backport in the commit message
• 4a17246|audit: store accept/accept-encoding/content-length audit log annotations: does not specify an upstream backport in the commit message
• 781b092|UPSTREAM: : Add OpenShift tooling, images, configs and docs: does not specify an upstream backport in the commit message
• 8979f1d|client-go/rest: move content type wiring from client to request: does not specify an upstream backport in the commit message
• ae2b06a|generated: does not specify an upstream backport in the commit message
• d26684b|Store "openshift.io/request-header-host" annotation in audit logs: does not specify an upstream backport in the commit message
• db61bcf|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.

[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/machine-api-operator#1306

[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/fd0725a0-960d-11ef-9b20-c6c69022f342-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#1362 openshift/machine-api-operator#1306

[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/081fe680-96da-11ef-91f4-cde4735e474b-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#1362 openshift/machine-api-operator#1306 openshift/cluster-network-operator#2550 openshift/prometheus-operator#312

[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/a7c78740-96f5-11ef-8917-56e896fcf5d0-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#1362 openshift/machine-api-operator#1306 openshift/cluster-network-operator#2550 openshift/prometheus-operator#312 openshift/cloud-network-config-controller#157

[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/20169390-9790-11ef-9369-5b6a6b14fab2-0