Repository navigation
scs-0219: note ingress-nginx retirement and add Gateway API recommendation - #1301
shresth-kumar-lal wants to merge 1 commit into
Conversation
…ation - Clarify in Ingress API section that ingress-nginx has entered upstream retirement and reference active CNCF alternatives (Traefik, Envoy Gateway). - Add Gateway API section explaining gateway.networking.k8s.io as the official upstream evolution of cluster ingress and traffic routing. - Add SHOULD recommendation in Decision for CSPs to support Gateway API and provide a default GatewayClass. Fixes SovereignCloudStack#1097 Signed-off-by: Shresth Kumar Lal <shresthkumarlal@gmail.com>
|
A quick note for reviewers (@mbuechse @garloff @depressiveRobot): I submitted this in-place update following the April 1 suggestion on #1097. However, reviewing the later history on #1166 and #1195, I noticed the May 7 SIG Std/Cert consensus that adding a normative If Team Container and the SIG prefer landing this via |
Description
Following the upstream retirement of
ingress-nginxand the maintainer consensus in #1097 to incorporate recommendations in place:ingress-nginxhas entered upstream retirement and listed active CNCF alternatives (Traefik, Envoy Gateway).gateway.networking.k8s.io) as the modern, role-oriented successor to the Ingress API.SHOULDclause recommending CSPs offer managed support for the Kubernetes Gateway API and a defaultGatewayClassresource.Fixes #1097.