feat(Grafana): K8s serviceaccount token as authorization .spec.client.useKubeAuth
#2137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the k8s ServiceAccount token projected in at
/var/run/secrets/kubernetes.io/serviceaccount/token
as authentication to Grafana instances.Users can configure [auth.jwt] to accept K8s ServiceAccounts and assign them roles depending on the name, namespace, etc in the JWT token and entirely disable the default Grafana admin account.
TODO
Maybe as a separate PR so it does not show in the docs until released with
v5.20.0
tls_client_ca
andjwk_set_bearer_token_file
grafana#109095Questions:
useKubeAuth
anduseJWTAuth
are both a bit vagueWould help a lot for usability as the the full setup can be handled in the
Grafana
CR