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

Bump kuberentes_metadata_filter plugin version #332

Closed
wants to merge 3 commits into from

Conversation

DevAndrewGeorge
Copy link

For those of us using the Docker image provided in this repo in AWS EKS, we've received a notice:

We have identified applications running in one or more of your Amazon EKS clusters that are not refreshing service account tokens. Applications making requests to Kubernetes API server with expired tokens will fail. You can resolve the issue by updating your application and its dependencies to use newer versions of Kubernetes client SDK that automatically refreshes the tokens.

The library/plugin causing triggering this notification has since been patched.

This PR bumps the version of affected plugin to resolve the issue in the relevant image.

(It also seems that Gemfile.lock hasn't been updated in a while.)

Bumping kuberentes_metadata_filter plugin version to support
Kubernetes 1.21+ BoundServiceAccountTokenVolume service account
token refresh.
@vmwclabot
Copy link
Member

@DevAndrewGeorge, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

Bumping kuberentes_metadata_filter plugin version to support
Kubernetes 1.21+ BoundServiceAccountTokenVolume service account
token refresh.

Signed-off-by: John Doe <ageorge@gumgum.com>
@vmwclabot
Copy link
Member

@DevAndrewGeorge, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants