User should be able to drop a path in the ingress level

[RamyChaabane]

Describe the feature

Hello there,

Today, to drop a path, you need to implement a route that returns 404 http code status when invoking your Knative service on that path. If you have configured scale to zero feature, this behaviour is not optimal as your pod will scale and you will be waiting for a few seconds (cold start time + time till your pod is in runnig state) for your path to be dropped.

I think we should be doing that in the ingress level without invoking the service

[nak3]

Thank you, Ramy! I think we have some points to be discussed. For example, I am thinking something likes these:

For use-case:

• Is there anyone else who wants/wanted to have this feature? It is not possible to manage this somehow - like extra front-end proxy or something?
• It will be optimal but it just returns 404 error code. We should consider more practical design?
  • i.e - From the web browser, users will get a blank page which is weird I think.

For implementations:

• This is possible to implement only on Ingress side, isn't it?
• This should be supported in not only Kourier but all Ingress?

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

[evankanderson]

I suspect the solution here is to make it easier to fit Knative "behind" a typical Ingress. Knative uses the Ingress feature set for HTTP request-level load balancing, but is not particularly intended to be in the HTTP routing game (doing so would substantially balloon the API).

We have some documentation for how do this for Istio or for Kong, but we don't have generic documentation for doing so.

[evankanderson]

/remove-lifecycle stale

[nak3]

Knative uses the Ingress feature set for HTTP request-level load balancing, but is not particularly intended to be in the HTTP routing game (doing so would substantially balloon the API).

I agreed on this before but https://github.com/knative/serving/issues/11997 is going to support the path-based routing, right? I think that we can implement this feature (#13228) easily once https://github.com/knative/serving/issues/11997 was implemented.