gimbal
gimbal copied to clipboard
Gimbal is an ingress load balancing platform capable of routing traffic to multiple Kubernetes and OpenStack clusters. Built by Heptio in partnership with Actapio.
**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,...
**Describe the solution you'd like** We are operating Gimbal cluster in our private cloud and got a request to get Gimbal support gRPC (http2) based endpoints as well. Manually change...
Add ability for discoverer to read in a configmap or args list of namespaces in which the discoverer should not watch for changes.
Currently, grafana dashboards are deployed via the [dashboard provisioning feature ](http://docs.grafana.org/administration/provisioning/#dashboards). This is great because the dashboards come pre-loaded with the grafana deployment. The downside, however, is that grafana does...
At launch, Gimbal requires that discovered Application VMs (OpenStack) and Pods (Kubernetes) must have routable IPs that can be reached from the Gimbal cluster. While this is sufficient for our...
**What steps did you take and what happened:** 1. I configured route consist of 1 OpenStack service (has 2 endpoints) with health check to ingressroute.yaml file and deployed it. 2....
Update Grafana deployment to the latest minor version, which was released ~ 2 weeks ago. Whats new: http://docs.grafana.org/v5.1/guides/whats-new-in-v5-1/
Use heptio/workgroup to improve handling of the multiple goroutines that are spawned in each of the discoverers. This will also help us to bubble up errors to main, and handle...
OpenStack resources have a couple of status fields that we might have to inspect to determine whether we should route traffic to that LB or endpoint. Load balancers have admin_state_up,...
Active health checking can have an impact on data plane performance. Look into this to better understand what the impact is, if any.