Update Ingress2Gateway 1.0 draft#54924
Conversation
|
/hold |
|
holding to give folks a chance to take a look |
|
cc @bexxmodd @ritazh @bridgetkromhout @jgreer @johananl @LiorLieberman @kkk777-7 @spencerhance @markuskobler |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Let's leave this held until the release date is confirmed. |
lmktfy
left a comment
There was a problem hiding this comment.
Ideally, split this:
- a PR to update the draft text
- a later PR (held until the release is confirmed) to publish the article
There was a problem hiding this comment.
To a newcomer, this sentence may be confusing, as it makes value judgements and assumptions about a past they did not experience: "The complexity of Gateway API can be daunting, but much of its design was a direct result of Ingress API shortcomings."
It might be more helpful to focus the topic with something like this, if accurate: "As the community migrates to Gateway API, we are documenting the gaps in Ingress API and redesigning to reduce complexity."
There was a problem hiding this comment.
hmm, I see your point. I don't think its correct to say that GWAPI is less complex, but we could say something like more modular, extensible, etc
There was a problem hiding this comment.
I think I like it better just saying that "gateway api is complex, these are some resources" That way its correct, precise, and doesn't make any value judgements.
There was a problem hiding this comment.
Maybe we'd like to reword:
With the Ingress-NGINX retirement scheduled for March 2026, the Kubernetes networking landscape is at a turning point.
given the likely publication date.
lmktfy
left a comment
There was a problem hiding this comment.
/label tide/merge-method-squash
/lgtm
/approve
|
LGTM label has been added. DetailsGit tree hash: 71f3e160dfbbbf88afb1921c8c0459b656d31bf6 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lmktfy The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold cancel |
* update with v1.0 warnigns * publish * Simplify * Remove publish * Retain original field order --------- Co-authored-by: Tim Bannister <193443691+lmktfy@users.noreply.github.com>
PublishAmend blog post for Ingress2Gateway 1.0.This also includes some last minute updates/changes since the draft went in