higress-group/higress

console 适配 Gateway API

Open

#992 opened on May 23, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (1,219 forks)github user discovery
area/outofboxgood-issuehelp wantedlevel/challenge

Repository metrics

Stars
 (9,036 stars)
PR merge metrics
 (Avg merge 7d 9h) (18 merged PRs in 30d)

Description

Why do you need it?

Is your feature request related to a problem? Please describe in details 对于使用 GW API 的用户，希望可以 console 配置的资源可以映射到 GW API 规范，就像目前映射到 Ingress API 规范一样

How could it be?

A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it. 通常对于同一个环境，应该只会使用 GW API 或者 Ingress API

Other related information

Add any other context or screenshots about the feature request here. GW API 可以允许我们配置多个监听端口，应对此 issue

Contributor guide

Research direction
Study the existing Ingress API mapping in the console, then adapt it to support Gateway API resources (e.g., Gateway, HTTPRoute). Ensure compatibility with multiple listeners as per issue #845.
Tech stack
go
Domain
apibackend
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.
3-5 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
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30