Update upstream dependencies to v1.31.0

[shizuchanw]

What this PR does / why we need it:
Cherry-picked commit on master to update upstream dependencies to v1.31.0

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes # N/A

[k8s-ci-robot]

Hi @shizuchanw. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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-sigs/prow repository.

[k8s-ci-robot]

@shizuchanw: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-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-sigs/prow repository.

[bryantbiggs]

/ok-to-test

[bryantbiggs]

/lgtm

[shizuchanw]

@jyotimahapatra @micahhausler Can I get an approved label? Thank you!

[bryantbiggs]

FYI - if you want to release this, you'll need to bump the version

aws-iam-authenticator/version.txt

Line 1 in af05168

0.6.22

otherwise, this is just adding the commit to the 0.6 branch (no release)

[shizuchanw]

FYI - if you want to release this, you'll need to bump the version

aws-iam-authenticator/version.txt

Line 1 in af05168

0.6.22

otherwise, this is just adding the commit to the 0.6 branch (no release)

Thank you!! Was gonna do it in a different PR but I guess it makes more sense to keep it in the same PR and add a new commit, just updated version.txt

[bryantbiggs]

/lgtm

[shizuchanw]

@jyotimahapatra @micahhausler Can I get an approved label? Thank you!

bump

[micahhausler]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: micahhausler, shizuchanw

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

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