Why is my Grafana service showing as "not found"? #4297
Replies: 4 comments 3 replies
-
I'm having the same issue -- on a fresh install, 11 different nginx ingress annotations are properly auto-discovered, but 3 of them are showing "Not Found", even though they were populated through auto-discovery. See screenshot: @mrsimonemms did you find an answer? |
Beta Was this translation helpful? Give feedback.
-
looks like this might be related to #3781? I will try it out an report back. |
Beta Was this translation helpful? Give feedback.
-
@vjm no, I've not yet found anything that solves it but your find in #3781 is a very good shout. I'll have a play with it (probably tomorrow) and see if that solves it. If it does, I'll raise a PR for an explanatory note in the docs. |
Beta Was this translation helpful? Give feedback.
-
My Grafana showing as "not found", but the service is working fine and the auto-discovered link is working too. Can someone explain where the status comes from please?
The ingress has the following annotations:
The ArgoCD ingress is working fine and configured similarly:
If there is some documentation which explains the nuances of the status, I've not been able to find it - if there is some, please point me in the right direction.
Beta Was this translation helpful? Give feedback.
All reactions