Update protobuf generated files to fix verify job

[dulek]

Seems like there was an upgrade of protoc (or libprotoc) in the CI's src
images. This causes the verify job to always fail as newly generated
files are different. This commit updates them to new version. Looks like
only the syntax of importing the packages is changed, so this commit
should not affect anything, beside unblocking the CI.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dulek
To complete the pull request process, please assign soltysh
You can assign the PR to them by writing /assign @soltysh in a comment when ready.

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

[sttts]

/hold

until we understand why the pb output changed.

@dulek which protoc version did you use? Which platform?

Does our CI verify protobuf output?

[danwinship]

Does our CI verify protobuf output?

yes, it's part of "make verify".

If you just make a dummy PR that doesn't change anything, it will currently fail ci/prow/verify, because the CI job thinks that the generated files should look different than they currently do in git

[dulek]

@sttts: And just to clarify - I just run the job manually and used whatever protoc was in verify container. I don't even know how to get that version, 3.0.x that verify-protobuf.sh requires is ancient anyway.

[sttts]

Go version of this repo is fixed now, to be 1.12.

[dulek]

@sttts: Does that fix the issue and render this commit obsolete?

[sttts]

#406 merged your pb changes already.

/close

[openshift-ci-robot]

@sttts: Closed this PR.

In response to this:

#406 merged your pb changes already.

/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/test-infra repository.

[sttts]

Created #417 to test that CI is fine now.

[sttts]

#417 is green. So we are fine again.