Thanos Ruler: got 401 Body: Unauthorized #25729
Labels
solved
stale
15 days without activity
tech-issues
The user has a technical issue about an application
thanos
triage
Triage is needed
Name and Version
bitnami/thanos 15.4.4
What architecture are you using?
amd64
What steps will reproduce the bug?
I'm busy setting up a Thanos stack. So far, things have been smooth sailing.
I've deployed the stack using the
thanos
Helm chart, provided by Bitnami. I also have thekube-prom-stack
deployed that is remote writing metrics into mythanos-receiver
(which has basic auth) - this is working perfectly.I've added basic authentication, via values.yaml:
which generates something similar to this:
which is injected into all my pods.
My problem:
I cannot get my Thanos Ruler to authenticate to my Thanos query API.
The error I receive:
My arguments passed into the Ruler container, noting that everything works perfectly fine without an authentication set:
The query and http.config are passed in via the Helm chart. So I can't manually specify an additional flag of http.config because of duplicate keys, which could include my
basic_auth
credentials as described here.How am I supposed to authenticate to the query API? Is there a simpler way that I may be missing?
And why is there a disparity between the different Thanos components? Why does the query API leverage
basic_auth
and the rest of the components requirebasic_auth_users
configuration?I appreciate any assistance!
Are you using any custom parameters or values?
Yes, here's a sample omitted for brevity
What is the expected behavior?
I expect the authentication to work out seamlessly, like the other components.
What do you see instead?
The text was updated successfully, but these errors were encountered: