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

Backport of auth/kubernetes: support for dynamically reloading short-lived tokens into release/1.9.x #13698

Merged
merged 5 commits into from Jan 22, 2022

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #13595 to be assessed for backporting due to the inclusion of the label backport/1.9.x.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.


This change is continuation to hashicorp/vault-plugin-auth-kubernetes#122 where support was added for dynamically reloading Kubernetes short-lived tokens for better Kubernetes 1.21+ compatibility. This change takes the feature into use in Vault.

  • Uplift new version of Kubernetes auth plugin that does not store the service account token persistently to Vault storage.
  • Update the documentation to recommend local token again when running Vault inside cluster.

Fixes #12855

Signed-off-by: Tero Saarni tero.saarni@est.tech

@hashicorp-cla
Copy link

hashicorp-cla commented Jan 19, 2022

CLA assistant check
All committers have signed the CLA.

@vercel vercel bot temporarily deployed to Preview – vault-storybook January 19, 2022 00:34 Inactive
@vercel vercel bot temporarily deployed to Preview – vault January 19, 2022 00:36 Inactive
@tvoran tvoran added this to the 1.9.3 milestone Jan 19, 2022
@tvoran
Copy link
Member

tvoran commented Jan 19, 2022

Just waiting on backporting to the kubernetes plugin's release branch, then I'll update this one.

tsaarni and others added 3 commits January 19, 2022 13:50
…#13595)

* auth/kubernetes: support for short-lived tokens

* Uplift new version of Kubernetes auth plugin that does not store the
  service account token persistently to Vault storage.

* Update the documentation to recommend local token again when running
  Vault inside cluster.

Signed-off-by: Tero Saarni <tero.saarni@est.tech>

* Added changelog entry

Signed-off-by: Tero Saarni <tero.saarni@est.tech>

* clarification to changelog entry, executed go mod tidy

* clarifications and added targeted release version
renamed changelog file to the backport pr number.
go get github.com/hashicorp/vault-plugin-auth-kubernetes@v0.11.4
go mod tidy
@tvoran tvoran force-pushed the backport/tsaarni/issue12855/similarly-rare-dove branch from ceae8da to 5cbc6de Compare January 19, 2022 22:51
@vercel vercel bot temporarily deployed to Preview – vault-storybook January 19, 2022 22:51 Inactive
@vercel vercel bot temporarily deployed to Preview – vault January 19, 2022 22:51 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook January 21, 2022 06:56 Inactive
@tvoran
Copy link
Member

tvoran commented Jan 21, 2022

Ok, I think this one is ready to go.

@tvoran tvoran merged commit 38c074a into release/1.9.x Jan 22, 2022
@tvoran tvoran deleted the backport/tsaarni/issue12855/similarly-rare-dove branch January 22, 2022 00:30
@sudermanjr
Copy link

Is there a way to use this currently via publicly-available images? I seem to see it should be available when 1.9.3 is released, but I got myself into a bit of a bind and could definitely use the fix sooner if there's an image available. I would also be very happy to test out a release candidate if one becomes available.

@tvoran
Copy link
Member

tvoran commented Jan 27, 2022

Hi @sudermanjr, unfortunately I don't think we're publishing any pre-release images yet. And yes, this change will be included in the 1.9.3 release, which should come out soon.

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.

None yet

6 participants