|
2 | 2 |
|
3 | 3 | * Issue: [#1709](https://github.com/kubernetes-sigs/gateway-api/issues/1709)
|
4 | 4 | * Status: Experimental
|
5 |
| -* Probationary Period: Re-evaluate in February 2024 |
| 5 | +* Probationary Period: Re-evaluate in April 2024 |
6 | 6 |
|
7 | 7 | ## TLDR
|
8 | 8 |
|
@@ -646,14 +646,31 @@ The following are items that **MUST** be resolved to move this GEP to
|
646 | 646 |
|
647 | 647 | - [x] some kind of basic level of display for the report data needs to exist.
|
648 | 648 | 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. |
650 | 655 | While this is probably sufficient during the `Experimental` phase, we need to
|
651 | 656 | re-evaluate this before `Standard` and see if this remains sufficient or if
|
652 | 657 | 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 |
654 | 663 | Arch][sig-arch-feedback]. Some time during the `experimental` phase needs to
|
655 | 664 | be allowed to continue to engage with SIG Arch and incorporate their feedback
|
656 | 665 | 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. |
657 | 674 |
|
658 | 675 | [sig-arch-feedback]:https://groups.google.com/g/kubernetes-sig-architecture/c/YjrVZ4NJQiA/m/7Qg7ScddBwAJ
|
659 | 676 |
|
|
0 commit comments