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

Support for BoundServiceAccountTokenVolume 1hr token refresh in k8s 1.21+ #242

Closed
bobmacks opened this issue May 24, 2022 · 3 comments
Closed
Labels
enhancement New feature or request

Comments

@bobmacks
Copy link

bobmacks commented May 24, 2022

What would you like to be added:
Support for BoundServiceAccountTokenVolume 1hr service account token refresh requirements for Kubernetes 1.21+

Why is this needed:
We use splunk/splunk-connect-for-kubernetes chart which uses splunk/fluentd-hec v1.2.13 by default.

Similar to feature request raised in fluent/fluent-bit and logzio/logzio-k8s and fabric8io/fluent-plugin-kubernetes_metadata_filter we are also receiving notifications from AWS indicating our EKS 1.21 cluster has enabled BoundServiceAccountTokenVolume feature by default and encountering numerous stale service account token notifications as a result.

There is an open PR from fabric8io/fluent-plugin-kubernetes_metadata_filter seeking to address this issue.

Can a similar feature be included in fluentd-hec to support hourly service account token refresh?

@hvaghani221 hvaghani221 added the enhancement New feature or request label May 30, 2022
@vinzent
Copy link
Contributor

vinzent commented May 31, 2022

Related to splunk/splunk-connect-for-kubernetes#768

@derek-miller-yohana
Copy link

The PR you mentioned has been closed in favor of the workaround in this PR, which is in the 2.11.1 release. I opened #251 hoping to get a release that uses that version.

@hvaghani221
Copy link
Contributor

Added support in 1.3.0 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants