search

solo-io / gloo

The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy
https://docs.solo.io/
Apache License 2.0
4.07k stars 434 forks source link

Gloo Fed: ingress discovery issue when edge monitoring service is enabled #7020

Open guydc opened 2 years ago

guydc commented 2 years ago

Gloo Edge Version

1.11.x

Kubernetes Version

No response

Describe the bug

If the dedicated monitoring service is enabled, Gloo Fed shows the following error message: "error":"1 error occurred:\n\t* Unsupported service type (ClusterIP) found for gateway service (gateway-proxy-monitoring-service │ [...]) on cluster\. The ingress IP is still discovered and present in the relevant GlooInstance resource.

Steps to reproduce the bug

Install Gloo Edge with dedicated monitoring service enabled. Register the Cluster with Gloo Fed.

Expected Behavior

This service should be ignored for discovery.

Additional Context

No response

github-actions[bot] commented 3 months ago

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.