You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this enhancement require public documentation?
I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)
Problem Statement
We are leveraging KIC's implementation of GatewayClass (httproutes) for configuring Kong. We are interested in defaulting the behavior of upstream target selection to the Kubernetes Service. This can be done for individual services via the ingress.kubernetes.io/service-upstream annotation. However, for us it would be awesome if there was a way to make that the default for all services.
Proposed Solution
We noticed that there is this solution that was implemented using IngressClass parameters. We tried setting this up but it doesn't seem to be compatible with the GatewayClass implementation. The GatewayClass spec indicates that a parametersRef can be passed, perhaps to this same end.
Additional information
We did try passing the ingress class parameter object as a reference to the GatewayClass, but that did not work.
Acceptance Criteria
[] Default value can be controlled for all upstream services, for the upstream-service annotation (and maybe others, like timeouts, retires, etc.) via KIC's GatewayClass implementation.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Does this enhancement require public documentation?
Problem Statement
We are leveraging KIC's implementation of GatewayClass (httproutes) for configuring Kong. We are interested in defaulting the behavior of upstream target selection to the Kubernetes Service. This can be done for individual services via the ingress.kubernetes.io/service-upstream annotation. However, for us it would be awesome if there was a way to make that the default for all services.
Proposed Solution
We noticed that there is this solution that was implemented using IngressClass parameters. We tried setting this up but it doesn't seem to be compatible with the GatewayClass implementation. The GatewayClass spec indicates that a parametersRef can be passed, perhaps to this same end.
Additional information
We did try passing the ingress class parameter object as a reference to the GatewayClass, but that did not work.
Acceptance Criteria
upstream-service
annotation (and maybe others, like timeouts, retires, etc.) via KIC's GatewayClass implementation.The text was updated successfully, but these errors were encountered: