Skip to content

Commit 2ac95e4

Browse files
authored
Merge pull request #2742 from shaneutt/shaneutt/gep-1709-updates-2024-01-26
Add graduation criteria for Conformance Profiles GEP (1709)
2 parents df978ef + cfa9a6a commit 2ac95e4

File tree

1 file changed

+20
-3
lines changed

1 file changed

+20
-3
lines changed

geps/gep-1709/index.md

Lines changed: 20 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
* Issue: [#1709](https://github.com/kubernetes-sigs/gateway-api/issues/1709)
44
* Status: Experimental
5-
* Probationary Period: Re-evaluate in February 2024
5+
* Probationary Period: Re-evaluate in April 2024
66

77
## TLDR
88

@@ -646,14 +646,31 @@ The following are items that **MUST** be resolved to move this GEP to
646646

647647
- [x] some kind of basic level of display for the report data needs to exist.
648648
It's OK for a more robust display layer to be part of a follow-up effort.
649-
- [ ] initially we were OK with storing reports in the Git repository as files.
649+
- for now we ended up with badges in our implementations page. We have
650+
[another effort](https://github.com/kubernetes-sigs/gateway-api/issues/2550)
651+
underway to build an even better display layer, but we consider this
652+
additive and the current display is sufficient for moving the project to
653+
standard.
654+
- [x] initially we were OK with storing reports in the Git repository as files.
650655
While this is probably sufficient during the `Experimental` phase, we need to
651656
re-evaluate this before `Standard` and see if this remains sufficient or if
652657
we want to store the data elsewhere.
653-
- [ ] We have been actively [gathering feedback from SIG
658+
- During the experimental phase this has not caused any significant issues,
659+
so for the purposes of calling this standard we're going to move forward
660+
as-is. It should be straightforward and reasonable to change the storage
661+
mechanism later as needs arise.
662+
- [x] We have been actively [gathering feedback from SIG
654663
Arch][sig-arch-feedback]. Some time during the `experimental` phase needs to
655664
be allowed to continue to engage with SIG Arch and incorporate their feedback
656665
into the test suite.
666+
- SIG Arch did not have any significant feedback during the experimental
667+
phase. In the same timespan the Network Policy group has started using our
668+
test suite and APIs as well, so it seems the overall approach has obvious
669+
merit, and doesn't appear to be redundant.
670+
- [ ] Finalize the report organization structure based on feedback during the
671+
experimental phase.
672+
- [ ] Base documentation must exist for implementations to run the tests via
673+
the CLI and via the Golang library.
657674

658675
[sig-arch-feedback]:https://groups.google.com/g/kubernetes-sig-architecture/c/YjrVZ4NJQiA/m/7Qg7ScddBwAJ
659676

0 commit comments

Comments
 (0)