You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
We applied grafana deployments on master branch. Grafana server can serve Contour, Gimbal Discovery and Envoy metrics dashboards.
On Contour and Gimbal Discovery dashboards, we can get each resources from selected namespace.
But, we can not select any namespaces on Envoy Metrics dashboard even if there are some active ingressroutes and namespaces on gimbal kubernetes cluster.
And, if we checkout Gimbal version 0.4.0 and downgrade Contour and Envoy pods, Grafana server works fine.
I think Contour or Envoy pods on Gimbal master branch cannot combine with Grafana pods because of its rbac or some settings.
What did you expect to happen:
All Grafana dashboards work fine and combine all active kubernetes namespaces.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
Gimbal Cluster Kubernetes version (use kubectl version): v1.14.2
@hmorikaw there may be some versioning issues here, the latest Contour changed how some metrics in the dashboard needed to work. There might be some tweaks that need to be brought over from that repo. I'll check and get back to you.
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
We applied grafana deployments on master branch. Grafana server can serve Contour, Gimbal Discovery and Envoy metrics dashboards.
On Contour and Gimbal Discovery dashboards, we can get each resources from selected namespace.
But, we can not select any namespaces on Envoy Metrics dashboard even if there are some active ingressroutes and namespaces on gimbal kubernetes cluster.
And, if we checkout Gimbal version 0.4.0 and downgrade Contour and Envoy pods, Grafana server works fine.
I think Contour or Envoy pods on Gimbal master branch cannot combine with Grafana pods because of its rbac or some settings.
What did you expect to happen:
All Grafana dashboards work fine and combine all active kubernetes namespaces.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): v1.14.2uname -a
): 4.4.0-146-genericThe text was updated successfully, but these errors were encountered: