Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service-upstream default controlled by GatewayClass parametersRef #6587

Open
2 tasks done
msmost opened this issue Nov 1, 2024 · 0 comments
Open
2 tasks done

Service-upstream default controlled by GatewayClass parametersRef #6587

msmost opened this issue Nov 1, 2024 · 0 comments

Comments

@msmost
Copy link

msmost commented Nov 1, 2024

Is there an existing issue for this?

  • I have searched the existing issues

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant