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.08k stars 437 forks source link

Knative-external-proxy health check issue #6785

Open podilavenky opened 2 years ago

podilavenky commented 2 years ago

Gloo Edge Version

1.11.x (latest stable)

Kubernetes Version

1.21.x

Describe the bug

Hi I deployed gloo with knative on AWS EKS Fargate. I am trying to use alb as ingress and added service name knative-external-proxy to it. Edited knative-external-proxy service type as NodePort. But health check is failing for alb. Health check is configured to use Http with port 80. Even I tried doing curl to knative-external-proxy pod ip with port 80 but getting connection refused message. Help me if I miss anything on configuration.

Steps to reproduce the bug

Followed below document https://docs.solo.io/gloo-edge/1.7.23/installation/knative/#:~:text=Using%20glooctl%20will%20install%20Knative,the%20dependencies%20on%20Istio%20removed.

Expected Behavior

Alb health check

Additional Context

No response

kevin-shelaga commented 2 years ago

Hello @podilavenky per the notice in the latest docs, knative support has been removed from gloo edge as of release 1.11

https://docs.solo.io/gloo-edge/latest/installation/knative/

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.