When to use multiple gatewayclasses

[davem-git]

Is there guidance or best practices on when multiple GatewayClasses are recommended?

From our understanding, most behavior is configured at the Gateway / listener / route level, and per-Gateway data-plane tuning can be handled via EnvoyProxy. Because of that, it’s not obvious when introducing additional GatewayClasses provides meaningful value.

Our current plan is a single GatewayClass, with multiple Gateways:

• external HTTPS gateway
• multiple external TCP gateways (to work around the 64 listener limit)
• an internal gateway

In what scenarios does it make sense to split these into separate GatewayClasses instead of keeping one class and multiple Gateways? Are there concrete examples where multiple GatewayClasses are preferred or required?

[arkodg]

if you were using mergedGateways you could split up infra using 2 GatewayClasses