rueian/gke-hubble-export

Install hubble-ui on GKE Dataplane V2

GKE Hubble Export

Currently, Hubble UI can't be install on the GKE Dataplane V2 because GKE doesn't export cilium agent's observer service and peer service through tcp socket which is required by the Hubble Relay.

So, this repo is just a simple grpc proxy that re-export the above services from the local domain socket to a tcp socket. And it can be consumed by the Hubble Relay on the GKE Dataplane V2, thus Hubble UI can be install.

Warning

The current implementation re-exports the above services without mTLS. Feel free to modify it.

Example

# create gke with --enable-dataplane-v2
gcloud beta container clusters create "cluster-1" \
  --cluster-version "1.21.6-gke.1500" \
  --enable-dataplane-v2

# deploy gke-hubble-export + hubble-relay + hubble-ui in the default namespace.
kubectl apply -f example.yaml

# access the hubble-ui
kubectl port-forward svc/hubble-ui 8081:80

gke-hubble-export's Issues

Prometheus metrics

Hi,

First, thanks for your project ! It works very well

I was asking if it was possible to enable Prometheus metrics of Hubble ?

Thanks

The project should define the license on which it is made available

We want to use the project, unfortunately, there is no license provided. It is a showstopper for commercial use.
It would be beneficial if the proper license was added. the most suitable for our case would be MIT, Apache-2.0 or BSD.

bug: PEER_ADDED peer notification is not being sent to hubble-relay

What's happening?

• Hubble Relay connects to all node peers on a restart
• Hubble Relay receives PEER_DELETED notifications and reacts on them when the autoscaler removes nodes
• When the autoscaler adds nodes Hubble Relay does not react, logs on Hubble Relay show no PEER_ADDED notification even though the exporter is up and running, can only be resolved with a restart.

Versions

• gke-hubble-export image built from master and deployed via the helm chart (1a7aa96)
• K8s version - v1.26.5-gke.1200