-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
inputs.prometheus still requires cluster level permissions when scoped to a namespace #13876
Comments
@Ivaylogi98 or @redbaron are either of you able to run telegraf without cluster level permissions? I know you confirmed in the issue and PR, but @n0coast seems to not be able to. |
@n0coast , do you have any other instances of |
Fix you are looking for is #13627 , which I think is in 1.28, but wasn't backported to 1.27 |
@n0coast , looking at the error closer, I think it comes from the part where it lists all namespaces. It is for This can be improved, I agree |
Still facing the same issue with Config:
|
Hello, Im facing the same issue with 1.29. |
@n0coast, @Thrinadh-Kumpatla and @valeraBr please test the binary in PR #14871, available once CI finished all tests... Let me know if this fixes the issue! |
Can someone please test the PR!?!? |
@srebhan I've tested the raised PR, it works now with the provided binaries. No cluster scope errors anymore. Thanks. |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.27.4, container: docker.io/library/telegraf:1.27-alpine, kubernetes v1.26
Docker
No response
Steps to reproduce
Add the following chart dependency:
Configure telegraf role as follows:
Install helm chart with telegraf dependency included, with inputs.prometheus configured and scoped to the namespace application and telegraf are running in.
Expected behavior
Metrics are scraped without issue in the configured namespace.
Actual behavior
telegraf attempts to list namespaces at cluster level and is unable, loudly complains in logs
Additional info
Similar to #12780, but we're using a more recent version of telegraf which should include this fix: #13063
The text was updated successfully, but these errors were encountered: