Update google.golang.org/api version to get NEG IPv6 fields

[gauravkghildiyal]

No description provided.

[google-oss-prow]

Hi @gauravkghildiyal. Thanks for your PR.

I'm waiting for a GoogleCloudPlatform member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[spencerhance]

/ok-to-test

[gauravkghildiyal]

/hold

[gauravkghildiyal]

There's some test failures upstream. Will wait for them to get fixed.

[gauravkghildiyal]

/unhold

[gauravkghildiyal]

/retest

[gauravkghildiyal]

Looks like pull-k8s-cloud-provider-test uses a very old version of golang.

For starters, I'll update this to a new image.

[aojea]

Looks like pull-k8s-cloud-provider-test uses a very old version of golang.

I think that the problem is that there some dependencies that needs to be updated too

[aojea]

you should not need to use these replace block, replace is for pinning dependencies

[aojea]

can you try to remove the entire replace block and run go mod tidy && go mod vendor again?

[gauravkghildiyal]

>you should not need to use these replace block, replace is for pinning dependencies
While I'm not aware of the context of why that was done, but I did see a commit from @spencerhance to explicitly pin them. Spencer, can you clarify if this is still needed?

>can you try to remove the entire replace block and run go mod tidy && go mod vendor again?
Gave this a shot. It failed with another reason. I believe the explanation in #89 (comment) should be the cause for this too.

[spencerhance]

We probably don't need to pin dependencies anymore. We originally did this when we first migrated to go modules to make sure that dependencies wouldn't get updated.

[gauravkghildiyal]

Thanks Spencer! I removed the pinned dependencies.

[gauravkghildiyal]

Thanks for looking into this Antonio!

I tried running the tests locally and they pass for me without any additional changes.

Why I believed it was the older go version was because the error messages are complaining about objects not found in the go standard library:

Looks like these were initially available in the ioutil package but then deprecated and moved to the io package in go1.16. We're using kubekins-e2e image from 2019 and looks like go1.16 wasn't released then:

[gauravkghildiyal]

/retest

[aojea]

Looks like these were initially available in the ioutil package but then deprecated and moved to the io package in go1.16. We're using kubekins-e2e image from 2019 and looks like go1.16 wasn't released then:

:/

[gauravkghildiyal]

/retest

[bowei]

Gaurav -- can you update and rerun to regenerate the changed files.

[gauravkghildiyal]

@bowei

Gaurav -- can you update and rerun to regenerate the changed files.

Done

[aojea]

LGTM

[bowei]

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bowei, gauravkghildiyal

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

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