Skip to content

How can I configure Dedicated Gateway per Knative Service #16394

@AyushChothe

Description

@AyushChothe

In what area(s)?

/area API
/area autoscale
/area networking

Question

Is there a way to configure a dedicated Gateway per Knative Service, instead of using a single shared Gateway for all services?

What I want

I want to specify the Gateway name via an annotation on the Knative Service, so each service can be routed through its own Gateway.

This would let me apply per-service policies, such as:

  • firewall rules
  • rate limiting
  • access logs
  • security policies

Desired request flow

Option 1: Shared gateway → Dedicated per-service gateway → Knative

  1. The main/shared gateway receives the incoming request.

  2. The request is forwarded to a dedicated gateway for that Knative Service.

  3. The dedicated gateway applies per-service policies (firewall, rate limiting, etc.).

  4. The request is forwarded into the Knative data plane:

    • directly to the queue-proxy (if pods are running), or
    • to the Activator (if the service is scaled to zero)

Option 2: Dedicated per-service gateway as the entrypoint → Knative

  1. The incoming request goes directly to the dedicated gateway for that Knative Service.

  2. The dedicated gateway applies per-service policies (firewall, rate limiting, etc.).

  3. The request is forwarded into the Knative data plane:

    • directly to the queue-proxy (if pods are running), or
    • to the Activator (if the service is scaled to zero)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions