✅ Hubble was successfully enabled!
    /¯¯\
 /¯¯\__/¯¯\    Cilium:             3 errors
 \__/¯¯\__/    Operator:           OK
 /¯¯\__/¯¯\    Envoy DaemonSet:    disabled (using embedded mode)
 \__/¯¯\__/    Hubble Relay:       1 errors, 1 warnings
    \__/       ClusterMesh:        disabled

Deployment        hubble-relay       Desired: 1, Unavailable: 1/1
DaemonSet         cilium             Desired: 2, Ready: 2/2, Available: 2/2
Deployment        cilium-operator    Desired: 1, Ready: 1/1, Available: 1/1
Containers:       cilium             Running: 2
                  cilium-operator    Running: 1
                  hubble-relay       Pending: 1
Cluster Pods:     4/4 managed by Cilium
Image versions    cilium             quay.io/cilium/cilium-ci:cc0ebab9c40eb3f0a3228ddfce6bd443d8ef9342: 2
                  cilium-operator    quay.io/cilium/operator-generic-ci:cc0ebab9c40eb3f0a3228ddfce6bd443d8ef9342: 1
                  hubble-relay       quay.io/cilium/hubble-relay-ci:cc0ebab9c40eb3f0a3228ddfce6bd443d8ef9342: 1
Errors:           hubble-relay       hubble-relay                     1 pods of Deployment hubble-relay are not ready
                  cilium             cilium-g8ng4                     controller cilium-health-ep is failing since 1m32s (2x): Get "http://10.242.0.191:4240/hello": dial tcp 10.242.0.191:4240: connect: no route to host
                  cilium             cilium-t92fn                     controller cilium-health-ep is failing since 24s (5x): Get "http://10.242.1.38:4240/hello": dial tcp 10.242.1.38:4240: connect: no route to host
                  cilium             cilium-t92fn                     controller endpoint-1321-regeneration-recovery is failing since 12s (1x): regeneration recovery failed
Warnings:         hubble-relay       hubble-relay-54b48dcf58-zpshd    pod is pending

Error: Unable to determine status:  timeout while waiting for status to become successful: context deadline exceeded
Error: Process completed with exit code 1.