Skip to content

Conversation

@vadimalekseev
Copy link
Member

Describe Your Changes

Add support for dynamic token and certificates reloading.
Fixes #995.

Checklist

The following checks are mandatory:


## tip

* FEATURE: [Kubernetes Collector](https://docs.victoriametrics.com/victorialogs/vlagent/#collect-kubernetes-pod-logs): add support for dynamic token and certificates reloading. Previously, vlagent only read credentials at startup, which led to authentication errors after token rotation. See [#995](https://github.com/VictoriaMetrics/VictoriaLogs/issues/995).
Copy link
Contributor

Choose a reason for hiding this comment

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

BUGFIX?

Copy link
Member Author

Choose a reason for hiding this comment

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

Changed to BUGFIX. But to me, it is a feature, since we didn't expect vlagent to be able to rotate Kubernetes tokens.

@vadimalekseev vadimalekseev force-pushed the reload-k8s-creds branch 2 times, most recently from 80ade1c to bb69c93 Compare January 14, 2026 11:21
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.

401 unauthorized error from kube-apiserver, possibly linked with service account token rotation?

2 participants