envoyproxy/gateway

Support MergeType in ClientTrafficPolicy

Open

#6,735 opened on Aug 8, 2025

View on GitHub
 (14 comments) (8 reactions) (0 assignees)Go (802 forks)auto 404
help wanted

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (Avg merge 14d 16h) (153 merged PRs in 30d)

Description

Description:

Describe the desired behavior, what scenario it enables and how it would be used.

Add support for merging policies applied at various levels similar to what exists for BTP https://gateway.envoyproxy.io/latest/concepts/gateway_api_extensions/backend-traffic-policy/#policy-merging

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Contributor guide

Research direction
Study existing BackendTrafficPolicy merging logic and apply similar approach to ClientTrafficPolicy, ensuring correct policy hierarchy and conflict resolution.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
KubernetesGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40