-
Notifications
You must be signed in to change notification settings - Fork 152
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
3.7.0 broke auth_token #420
Comments
Hello! Could you share your Kubernetes config files? We tested several scenarios before releasing 3.7.0 and did not notice any issues. |
This is the grafana.ini in the Kube CM:
Here is the env variables that the grafana pod has:
here is the env values the renderer has:
|
I don't have a lot of knowledge around Kubernetes but after a few tests, I would say this is incorrect:
And should be replaced with:
With the image renderer 3.6.4, you didn't use your Kubernetes secret but the string:
In 3.7.0, it broke because I had to chose a separator when allowing multiple tokens and decided to use the whitespace character as it's usually not used in authentication tokens. |
Thanks, I'll let the rest of my team know, I may provide a patch so that this works correctly in the helm chart at least. |
What happened:
An unrelated change pushed the version of grafana-image-renderer in my environment to 3.7.0 which is ok but suddenly it started to receive 401 unauth responses from grafana. A rollback to 3.6.4 fixed this.
I did try hardcoding the token to
test
on grafana and grafana-image-renderer and it was still getting the same thing.What you expected to happen:
3.7.0 worked with existing functioning configuration.
How to reproduce it (as minimally and precisely as possible):
Upgrade to 3.7.0 as far as I can see. Happy to provide more detail if required.
Anything else we need to know?:
Running on kubernetes using the grafana provided chart which defaults to
latest
.Environment:
The text was updated successfully, but these errors were encountered: