Arko Dasgupta

@davem-git with #4021 (which is now available with `v0.0.0-latest`) you may not need explicit health checks because we've reduced the time to detect failure for the envoy endpoints

> hey @arkodg , just a basic doubt > > is there no need for adding pod readiness gates on namespace where envoy proxies are running(proxies receiving traffic via nlb...

im a +1 to return 500 if a CTP, BTP or EETP policy tied to a route cannot be translated . This would match the behavior of filters https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io%2fv1.HTTPRouteFilter ```...

closing this PR since its become inactive, feel free to reopen if you're still working on it

hey @zirain your suggestion is the best long term solution, I haven't felt the pain of reading/editing this code so I'd mark this tech debt as lower priority, but maybe...

@zirain with this approach, my only concern is resources required for e2e, we are already limited by the GHA runner size, and adding another registry to run will make it...

> i didn't add a local registry now, using kind load instead. ah cool, does this work for devs with Mac envs as well ?

also related to https://github.com/envoyproxy/gateway/issues/2054

got for it @kkk777-7 !

Thanks @kkk777-7 yes option 2 is what we have implemented in the project ( Gateway and Route) , this feature will add another level