Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

gateway-api k8s-sig-network kubernetes networking sig-network
23 Open Issues Need Help Last updated: Jul 2, 2026

Open Issues Need Help

View All on GitHub
kind/feature good first issue help wanted lifecycle/active

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
good first issue priority/important-longterm kind/documentation

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
Modernize API markers about 2 months ago
help wanted kind/cleanup

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
good first issue help wanted kind/documentation

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network

AI Summary: This GitHub issue reports a syntax error in the Gateway API documentation, specifically within the 'HTTP query parameter matching' guide. The `apiVersion` field in a YAML example is incorrectly written as `gateway.networking.k.io/v1` and needs to be corrected to `gateway.networking.k8s.io/v1` by adding '8s'.

Complexity: 1/5
good first issue help wanted kind/documentation

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
help wanted kind/documentation lifecycle/frozen triage/accepted

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
kind/feature good first issue priority/backlog needs-triage

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
kind/bug good first issue help wanted

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
good first issue help wanted kind/documentation

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
kind/feature help wanted priority/backlog

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
help wanted priority/important-soon kind/documentation needs-triage

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
kind/feature help wanted lifecycle/stale priority/backlog triage/accepted

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
help wanted priority/important-soon kind/documentation

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
kind/bug good first issue help wanted

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
good first issue help wanted area/conformance-test

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
kind/bug help wanted priority/important-soon kind/documentation triage/accepted

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
help wanted priority/critical-urgent v1.4-release/subtask

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
help wanted lifecycle/active needs-triage triage/accepted area/conformance-test

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network
good first issue help wanted kind/documentation

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network

AI Summary: The task is to fix a copy-paste error in the Go documentation (godoc) for the `backendTLSPolicy` within the Kubernetes Gateway API project. This involves identifying and removing duplicate text in the `backendtlspolicy_types.go` file, potentially requiring coordination with @LiorLieberman to confirm the error and ensure the fix doesn't introduce new issues.

Complexity: 2/5
kind/bug good first issue help wanted

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

Go
#gateway-api#k8s-sig-network#kubernetes#networking#sig-network