Grandfather GEPs 1324, 1427, and 1686 into not needing graduation requirements, as a first step toward merging these three into a single GAMMA GEP (now that we think we're in a place where we can actually do that) post-0.8.0.

Signed-off-by: [email protected]

Author: kflynn

geps/gep-1324.md

@@ -3,6 +3,12 @@
 * Issue: [#1324](https://github.com/kubernetes-sigs/gateway-api/issues/1324)
 * Status: Experimental
 
+> **Note**: This GEP is exempt from the [Probationary Period][expprob] rules
+> of our GEP overview as it existed before those rules did, and so it has been
+> explicitly grandfathered in.
+
+[expprob]:https://gateway-api.sigs.k8s.io/geps/overview/#probationary-period
+
 ## Overview
 
 Gateway API represents the next generation of traffic routing APIs in Kubernetes. While most of the current work for Gateway API is focused on the ingress use-case, support for service mesh implementations within the spec would be advantageous to the greater community. Therefore, this GEP serves as the genesis for developing common patterns for using Gateway API for east/west traffic within a mesh implementation.
@@ -165,10 +171,3 @@ These are goals that we aren’t explicitly excluding, but will reconsider at a
 * Heterogenous deployment targets (e.g VMs, serverless)
 * Deployment models (e.g. installation, mesh upgrades)
 
-## Graduation Criteria
-
-The following are items that **MUST** be resolved to move this GEP to
-`Standard` status (and before the end of the probationary period):
-
-...
-

geps/gep-1426.md

@@ -3,6 +3,12 @@
 * Issue: [#1294](https://github.com/kubernetes-sigs/gateway-api/issues/1294)
 * Status: Experimental
 
+> **Note**: This GEP is exempt from the [Probationary Period][expprob] rules
+> of our GEP overview as it existed before those rules did, and so it has been
+> explicitly grandfathered in.
+
+[expprob]:https://gateway-api.sigs.k8s.io/geps/overview/#probationary-period
+
 ## Overview
 
 Similar to how `xRoutes` bind to `Gateways` and manage North/South traffic flows in Gateway API’s ingress use-case, it would be natural to adopt a similar model for traffic routing concerns in service mesh deployments. The purpose of this GEP is to add a mechanism to the Gateway API spec for the purpose of associating the various `xRoute` types to a service mesh and offering a model for service owners to manage traffic splitting configurations.
@@ -467,10 +473,3 @@ An initial iteration of this GEP had the ability to omit a `backendRef` and have
 This has been removed due to inconsistency with Gateway `parentRefs` and tight coupling of the "frontend" and "backend" roles.
 
 Implementations MUST respect the standard `backendRef` rules as defined by the existing spec.
-
-## Graduation Criteria
-
-The following are items that **MUST** be resolved to move this GEP to
-`Standard` status (and before the end of the probationary period):
-
-...

geps/gep-1686.md

@@ -3,6 +3,12 @@
 - Issue: [#1686](https://github.com/kubernetes-sigs/gateway-api/issues/1686)
 - Status: Experimental
 
+> **Note**: This GEP is exempt from the [Probationary Period][expprob] rules
+> of our GEP overview as it existed before those rules did, and so it has been
+> explicitly grandfathered in.
+
+[expprob]:https://gateway-api.sigs.k8s.io/geps/overview/#probationary-period
+
 ## TLDR
 
 This testing plan specifies a new set of tests to define a "Mesh" [conformance profile](https://github.com/kubernetes-sigs/gateway-api/issues/1709).
@@ -106,10 +112,3 @@ Consumer routes have priority over producer routes.
 
 Filters have the same effects on requests as any implementation. Gateway API conformance test framework can be
 refactored to extract checks on filter behavior for use on both GAMMA and Gateway API tests.
-
-## Graduation Criteria
-
-The following are items that **MUST** be resolved to move this GEP to
-`Standard` status (and before the end of the probationary period):
-
-...