Skip to content

Update SCS-0219 after retirement of ingress-nginx and add Gateway API#1166

Open
lucasrattz wants to merge 1 commit into
SovereignCloudStack:mainfrom
lucasrattz:main
Open

Update SCS-0219 after retirement of ingress-nginx and add Gateway API#1166
lucasrattz wants to merge 1 commit into
SovereignCloudStack:mainfrom
lucasrattz:main

Conversation

@lucasrattz

Copy link
Copy Markdown

This pull request fixes #1097

Signed-off-by: Lucas Rattz <lucas.rattz@syself.com>
@depressiveRobot depressiveRobot added standards Issues / ADR / pull requests relevant for standardization & certification KaaS Issues or pull requests relevant to the SCS KaaS layer. labels May 4, 2026
@depressiveRobot depressiveRobot requested a review from jschoone May 4, 2026 14:08
@depressiveRobot

Copy link
Copy Markdown
Contributor

Thank you for the PR. Looks good to me from a formal point of view. However, I think someone from the Team Container should have a look here and review it. @jschoone @janiskemper

@berendt

berendt commented May 4, 2026

Copy link
Copy Markdown
Contributor

Don't we need a new version of this document here?

https://docs.scs.community/standards/scs-0001-v1-sovereign-cloud-standards#stabilized-phase-stable

"If a breaking change to an existing SCS document is deemed necessary, a new document with a new number shall be created and the old document SHOULD be deprecated."

@depressiveRobot

Copy link
Copy Markdown
Contributor

To me, this is more about a fix and adding a recommendation than a breaking change. So no need for a new version, IMO.

@jklare

jklare commented May 4, 2026

Copy link
Copy Markdown
Contributor

Since the Ingress API will continue to exist (https://gateway-api.sigs.k8s.io/faq/#will-gateway-api-replace-the-ingress-api) and the Gateway API is basically just an entirely new and independent parallel implementation, we can probably not just replace one with another in the standards (since this is not an update, but a switch towards another implementation).

@mbuechse

mbuechse commented May 4, 2026

Copy link
Copy Markdown
Contributor

@jklare You're right. The point here is that we're only replacing one recommendation by another (if I'm not mistaken). This is not a breaking change, because every test subject that passes the old version will also pass the new one. The update is with respect to Traefik instead of nginx.

@berendt

berendt commented May 5, 2026

Copy link
Copy Markdown
Contributor

Adding a new normative SHOULD ("CSPs SHOULD offer support for the Gateway API …") is, in my understanding, a substantive extension of the normative requirements for CSPs, which requires a v2 if the document has already been stabilized.

@mbuechse

mbuechse commented May 5, 2026

Copy link
Copy Markdown
Contributor

@berendt If this matter is so controversial, we should discuss it more. I added it to the agenda of this week's SIG Std/Cert.

@mbuechse

mbuechse commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

@lucasrattz The SIG Std/Cert on May 7 has decided that a new major version is desired. I have implemented this in #1195. Please tell me if you're okay with me copying your text in this way. I suppose I can add a stanza (such as Co-authored-by) to the commit, or something similar. Please tell me what works for you.

@lucasrattz

Copy link
Copy Markdown
Author

@lucasrattz The SIG Std/Cert on May 7 has decided that a new major version is desired. I have implemented this in #1195. Please tell me if you're okay with me copying your text in this way. I suppose I can add a stanza (such as Co-authored-by) to the commit, or something similar. Please tell me what works for you.

Yes, that's fine.

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

Labels

KaaS Issues or pull requests relevant to the SCS KaaS layer. standards Issues / ADR / pull requests relevant for standardization & certification

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Other] Update SCS-0219 after retirement of ingress-nginx and add Gateway API

5 participants