Update k8s apimachinery

[mshitrit]

Fixes http/2 CVE

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

This pull-request has been approved by: mshitrit

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

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

[mshitrit]

/test ?

[openshift-ci]

@mshitrit: The following commands are available to trigger required jobs:

• /test 4.12-ci-index-self-node-remediation-bundle
• /test 4.12-images
• /test 4.12-openshift-e2e
• /test 4.12-test
• /test 4.13-ci-index-self-node-remediation-bundle
• /test 4.13-images
• /test 4.13-openshift-e2e
• /test 4.13-test
• /test 4.14-ci-index-self-node-remediation-bundle
• /test 4.14-images
• /test 4.14-openshift-e2e
• /test 4.14-test

Use /test all to run all jobs.

In response to this:

/test ?

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.

[mshitrit]

/test 4.12-openshift-e2e

[razo7]

/lgtm

[mshitrit]

/cherry-pick release-0.5

[openshift-cherrypick-robot]

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

In response to this:

/cherry-pick release-0.5

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.

[mshitrit]

/cherry-pick release-0.7

[openshift-cherrypick-robot]

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

In response to this:

/cherry-pick release-0.7

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.

[openshift-cherrypick-robot]

@mshitrit: #145 failed to apply on top of branch "release-0.5":

Applying: Update k8s.io/apimachinery
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
Falling back to patching base and 3-way merge...
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update k8s.io/apimachinery
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.5

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.

[openshift-cherrypick-robot]

@mshitrit: new pull request created: #146

In response to this:

/cherry-pick release-0.7

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.