envoyproxy/gateway

docs: Add a Common Problems section

Open

#6,146 opened on May 21, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (802 forks)auto 404
documentationhelp wanted

Repository metrics

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

Description

Description:

Describe the issue.

One example to highlight here is how withUnderscoresAction defaults to Deny to adhere to best practises but surprises users coming from the nginx-ingress world withUnderscoresAction

Example https://github.com/envoyproxy/gateway/discussions/6127#discussioncomment-13225360

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Contributor guide

Research direction
Review the linked discussion (#6127) to understand the issue with `withUnderscoresAction` defaulting to `Deny`, then add a 'Common Problems' section in the documentation explaining this behavior and how to configure it.
Tech stack
gokubernetes
Domain
backendinfrastructure
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85