kubernetes-sigs / kubernetes-sigs/gateway-api

Add test and feature for extended backendRef ServiceImport

Open
#4,789 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/conformance-test
Dominant language
Go
Stars
3k
Forks
790
Avg merge
2d 15h
Merged PRs (30d)
45

Description

We claim on our APIs that we support ServiceImport as an extended backendRef. Yet, we have zero tests about it nor a feature name.

My suggestion is that we define a new union feature for ServiceImport so an implementation that claims support for it MUST support it on all the routes it supports (HTTPRoute, GRPCRoute) or even as a filter backend (eg.: a mirror)

Then we need a conformance test to assure that the multi cluster cases works, and that implementations that claim support for it can operate correctly.

Some references:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the referenced ServiceImport sections in apis/v1/httproute_types.go, apis/v1/grpcroute_types.go, and apis/v1/tlsroute_types.go, then find the existing feature definitions and conformance tests. Define the ServiceImport union feature and add coverage for multi-cluster use across HTTPRoute and GRPCRoute, including filter backends if supported by the scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, networking, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.