Help with Grafana configuration #1149
Unanswered
PoweredByPeople
asked this question in
Q&A
Replies: 2 comments
-
Haha. having exact same issue. This jsonnet is so cryptic. I think I will end up generating yams and than just edit them. How would I do it from here? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Tried to figure out the same thing, but I ended up patching the manifest: spec:
containers:
- env:
- name: GF_SERVER_ROOT_URL
value: <YOUR_URL_WITH_PATH>
- name: GF_SERVER_SERVE_FROM_SUB_PATH
value: "true" and creating a custom ingress resource also. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey there,
I'm relatively new to this project and to jsonnet. I'm trying to deploy grafana ingress on a url subpath but am having trouble getting the syntax/hierarchy correct. There are several examples in both this project and also the https://github.com/brancz/kubernetes-grafana project, however I am struggling to put it all together into one working jsonnet file in order to generate the correct manifest files.
I'm using kube-prometheus v0.8.0 and running on k3s v1.20.6+k3s1
My questions:
This is what I have so far: (I know it doesn't work, it's just a collection of things I've tried in order to convey what I'm trying to accomplish.)
Beta Was this translation helpful? Give feedback.
All reactions