envoyproxy/gateway

highlight deprecated fields in status

Open

#3,142 opened on Apr 9, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (802 forks)auto 404
help wantedkind/enhancement

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.

  • use the xPolicy.Status field to highlight any fields set in the xPolicy that are deprecated and will be removed soon
  • use the GatewayClass.Status field to highlight any fields set in EnvoyProxy that are deprecated and will be removed soon

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Contributor guide

Research direction
Investigate how the xPolicy and GatewayClass status fields are currently implemented. Look at existing examples of deprecation warnings in the codebase to understand the pattern. Then modify the status subresource to list deprecated fields based on the current API version.
Tech stack
go
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Clear
Prerequisites
GoKubernetesGateway API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50