Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cherry-pick: aws-iam-authenticator: Upgrade to v0.6.8 #2965

Merged
merged 1 commit into from
Mar 30, 2023

Conversation

jpmcb
Copy link
Contributor

@jpmcb jpmcb commented Mar 30, 2023

Fixes building on the tip of `develop` when using GOPROXY="direct".
v0.6.2 of aws-iam-authenticator has a Go code dependency on kubernetes 1.22.
There are privated GitHub repositories that can not be pulled down through the "direct" method.

Signed-off-by: John McBride <[email protected]>
(cherry picked from commit 64c93d243d5b33fefd99808049656ee649c59947)

Issue number:

N/a - related to #2956

Description of changes:

Upgrades the aws-iam-athenticator package to v0.6.8

Testing done:

N/a - see #2956

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

Fixes building on the tip of `develop` when using GOPROXY="direct".
v0.6.2 of aws-iam-authenticator has a Go code dependency on kubernetes
1.22. There are privated GitHub repositories that can not be pulled down
through the "direct" method.

Signed-off-by: John McBride <[email protected]>
(cherry picked from commit 64c93d2)
Copy link
Contributor

@stmcginnis stmcginnis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jpmcb jpmcb merged commit 055f1c3 into bottlerocket-os:1.13.x Mar 30, 2023
@jpmcb jpmcb deleted the cherry-pick-aws-iam-auth branch March 30, 2023 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants