Spike: Integrate Gateway API Routes with KongServiceFacade

[czeslavo]

Is there an existing issue for this?

• I have searched the existing issues

Problem Statement

Extracted from #5152.

As Gateway API Routes can have multiple backendRefs in a single rule it's not obvious how to handle the case when KongServiceFacade instance is used as one of many in such a group to make sure the original intention behind KongServiceFacade is persisted (only a single Kong Service is created in Kong for each KongServiceFacade).

Alternatives we might have:

• Create a separate Kong Service entity with Upstream Targets and break the promise to create only one Service in Kong for each KongServiceFacade.
• Forbid using KongServiceFacade in Gateway API Routes with multiple backendRefs.

Proposed Solution

• Investigate whether there is a possible use case for KongServiceFacade to be used as a backend in Gateway API Routes.
• Define how such integration should behave (focus on keeping the promise of 1-1 KongServiceFacade - Kong Service entity mapping).

Additional information

No response

Acceptance Criteria

• A way to integrate KongServiceFacade with Gateway API Routes is well defined and an issue for that exists.