This repository has been archived by the owner on May 13, 2024. It is now read-only.

refactor: migrate Ingress processing framework to be consistent with GatewayAPI #243

Open

reaver-flomesh opened this issue Mar 10, 2023 · 0 comments

Assignees

Labels

area/gateway-api area/ingress kind/enhancement priority/P3

Milestone

Collaborator

reaver-flomesh commented Mar 10, 2023

Please describe the Improvement and/or Feature Request

Scope (please mark with X where applicable)

New Functionality [ ]
Install [ ]
Gateway API - GatewayClass [ ]
Gateway API - Gateway [ ]
Gateway API - HTTPRoute [ ]
Gateway API - TLSRoute [ ]
Gateway API - TCPRoute [ ]
Gateway API - UDPRoute [ ]
Gateway API - PolicyReference [ ]
Ingress [ ]
Egress [ ]
MultiCluster [ ]
PIPY Control Plane [ ]
PIPY Script/Config [ ]
CLI Tool [ ]
Metrics [ ]
Certificate Management [ ]
Sidecar Injection [ ]
Logging [ ]
Debugging [ ]
Tests [ ]
Demo [ ]
CI System [ ]
Project Release [ ]

Possible use cases

reaver-flomesh added kind/enhancement area/ingress labels

reaver-flomesh added this to the v0.3.0 milestone

reaver-flomesh self-assigned this

reaver-flomesh added the area/gateway-api label

reaver-flomesh added the priority/P3 label

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.