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
Describe the bug
cyclops-ctrl 2023-12-14T19:41:07Z ERROR controller-runtime.source.EventHandler failed to get informer from cache {"error": "failed to get API group resources: unable to retrieve the complete list of server APIs: cyclops-ui.com/v1alpha1: Get "https://172.20.0.1:443/apis/cyclops-ui.com/v1alpha1\": dial tcp 172.20.0.1:443: connect: connection refused"}
To Reproduce
Steps to reproduce the behavior:
Deploy to k8s without the loadbalancer service
Update the REACT_APP_CYCLOPS_CTRL_HOST for cyclops-ctrl
Expected behavior
No error messages in the log when starting up
Additional context
port-forwarding to the container is working
istio-ingress is failing with a 503
The text was updated successfully, but these errors were encountered:
Hi @jaydeland, thanks for raising the issue! Could you describe how to reproduce the issue further since I couldn't get the error log on my local minikube? Could you also share what version of Cyclops you are running and on what kind of cluster?
Describe the bug
cyclops-ctrl 2023-12-14T19:41:07Z ERROR controller-runtime.source.EventHandler failed to get informer from cache {"error": "failed to get API group resources: unable to retrieve the complete list of server APIs: cyclops-ui.com/v1alpha1: Get "https://172.20.0.1:443/apis/cyclops-ui.com/v1alpha1\": dial tcp 172.20.0.1:443: connect: connection refused"}
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error messages in the log when starting up
Additional context
The text was updated successfully, but these errors were encountered: