Change Memorandum to a status and remove GEP type

Signed-off-by: Nick Young <[email protected]>
kubernetes-sigs · Dec 20, 2023 · 4e35a32 · 4e35a32
1 parent 1bc5fdb
commit 4e35a32
Show file tree

Hide file tree

Showing 41 changed files with 182 additions and 271 deletions.
diff --git a/geps/gep-1016.yaml b/geps/gep-1016.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1016
 name: GRPCRoute

diff --git a/geps/gep-1282.yaml b/geps/gep-1282.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1282
 name: Describing Backend Properties
@@ -8,9 +8,9 @@ authors:
   - youngnick
 relationships:
   obsoletedBy:
-  - number: 1897
-    name: BackendTLSPolicy - Explicit Backend TLS Connection Configuration
-    description: Implements just part of the Backend Properties GEP.
-  - number: 1911
-    name: Backend Protocol Selection
-    description: Protocol selection was one of the Backend Properties.
+    - number: 1897
+      name: BackendTLSPolicy - Explicit Backend TLS Connection Configuration
+      description: Implements just part of the Backend Properties GEP.
+    - number: 1911
+      name: Backend Protocol Selection
+      description: Protocol selection was one of the Backend Properties.
diff --git a/geps/gep-1323.yaml b/geps/gep-1323.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1323
 name: Response Header Filter

diff --git a/geps/gep-1324.md b/geps/gep-1324.md
@@ -1,8 +1,7 @@
 # GEP-1324: Service Mesh in Gateway API
 
 * Issue: [#1324](https://github.com/kubernetes-sigs/gateway-api/issues/1324)
-* Type: Memorandum
-* Status: Accepted
+* Status: Memorandum
 
 > **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

diff --git a/geps/gep-1324.yaml b/geps/gep-1324.yaml
@@ -1,18 +1,17 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1324
 name: Service Mesh in Gateway API
-type: Memorandum
-status: Accepted
+status: Memorandum
 authors:
   - keithmattix
   - markmc
   - kflynn
 relationships:
   updatedBy:
-  - number: 1426
-    name: xRoutes Mesh Binding
-    description: Adds initial Service binding proposal
-  - number: 1686
-    name: Mesh conformance testing plan
-    description: Adds initial Mesh conformance testing plan
+    - number: 1426
+      name: xRoutes Mesh Binding
+      description: Adds initial Service binding proposal
+    - number: 1686
+      name: Mesh conformance testing plan
+      description: Adds initial Mesh conformance testing plan
diff --git a/geps/gep-1364.yaml b/geps/gep-1364.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1364
 name: Status and Conditions Update

diff --git a/geps/gep-1426.yaml b/geps/gep-1426.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1426
 name: xRoutes Mesh Binding
@@ -10,6 +10,6 @@ authors:
   - keithmattix
 relationships:
   updates:
-  - number: 1324
-    name: Service Mesh in Gateway API
-    description: Adds initial Service binding proposal
+    - number: 1324
+      name: Service Mesh in Gateway API
+      description: Adds initial Service binding proposal
diff --git a/geps/gep-1619.yaml b/geps/gep-1619.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1619
 name: Session Persistence

diff --git a/geps/gep-1651.yaml b/geps/gep-1651.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1651
 name: Gateway Routability

diff --git a/geps/gep-1686.yaml b/geps/gep-1686.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1686
 name: Mesh conformance testing plan
@@ -11,6 +11,6 @@ authors:
   - kflynn
 relationships:
   updates:
-  - number: 1324
-    name: Service Mesh in Gateway API
-    description: Adds initial Mesh conformance testing plan
+    - number: 1324
+      name: Service Mesh in Gateway API
+      description: Adds initial Mesh conformance testing plan
diff --git a/geps/gep-1709.yaml b/geps/gep-1709.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1709
 name: Conformance Profiles

diff --git a/geps/gep-1742.yaml b/geps/gep-1742.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1742
 name: HTTPRoute Timeouts
@@ -14,6 +14,6 @@ authors:
   - sjberman
 relationships:
   updatedBy:
-  - number: 2257
-    name: Gateway API Duration Format
-    description: Adds a duration format for us in timeouts.
+    - number: 2257
+      name: Gateway API Duration Format
+      description: Adds a duration format for us in timeouts.
diff --git a/geps/gep-1748.yaml b/geps/gep-1748.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1748
 name: Gateway API Interaction with Multi-Cluster Services

diff --git a/geps/gep-1762.yaml b/geps/gep-1762.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1762
 name: In Cluster Gateway Deployments
@@ -9,5 +9,5 @@ authors:
   - frakbu
 relationships:
   updatedBy:
-  - number: 1867
-    name: Per-Gateway Infrastructure
+    - number: 1867
+      name: Per-Gateway Infrastructure
diff --git a/geps/gep-1867.yaml b/geps/gep-1867.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1867
 name: Per-Gateway Infrastructure
@@ -8,5 +8,5 @@ authors:
   - howardjohn
 relationships:
   updates:
-  - number: 1762
-    name: In Cluster Gateway Deployments
+    - number: 1762
+      name: In Cluster Gateway Deployments
diff --git a/geps/gep-1897.yaml b/geps/gep-1897.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1897
 name: BackendTLSPolicy - Explicit Backend TLS Connection Configuration
@@ -11,6 +11,6 @@ authors:
   - youngnick
 relationships:
   obsoletes:
-  - number: 1282
-    name: Describing Backend Properties
-    description: Implements just part of the Backend Properties GEP.
+    - number: 1282
+      name: Describing Backend Properties
+      description: Implements just part of the Backend Properties GEP.
diff --git a/geps/gep-1911.yaml b/geps/gep-1911.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 1911
 name: Backend Protocol Selection
@@ -10,6 +10,6 @@ authors:
   - frankbu
 relationships:
   obsoletes:
-  - number: 1282
-    name: Describing Backend Properties
-    description: Protocol selection was one of the Backend Properties.
+    - number: 1282
+      name: Describing Backend Properties
+      description: Protocol selection was one of the Backend Properties.
diff --git a/geps/gep-2162.yaml b/geps/gep-2162.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 2162
 name: Supported features in GatewayClass Status

diff --git a/geps/gep-2257.yaml b/geps/gep-2257.yaml
@@ -1,14 +1,13 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 2257
 name: Gateway API Duration Format
 type: API
 status: Experimental
 authors:
-  - 
+  - kflynn
 relationships:
   updates:
-  - number: 1742
-    name: HTTPRoute Timeouts
-    description: Adds a duration format for us in timeouts.
-
+    - number: 1742
+      name: HTTPRoute Timeouts
+      description: Adds a duration format for us in timeouts.
diff --git a/geps/gep-2659.md b/geps/gep-2659.md
@@ -8,24 +8,18 @@
 
 ## TLDR
 
-This GEP clarifies some details about GEPs, and adds relationships and new
-status types.
+This GEP clarifies some details about GEPs, and adds relationships and a new
+status.
 
 
 ## Goals
 
 - Enumerate how we should use RFC2119 language
 - Add relationships between GEPs
 - Add a metadata YAML schema for GEPs, including the new relationships
-- Add some new status types to cover some only recently noticed cases
+- Add a new status to cover some only recently noticed cases
 - Update existing documentation outside this GEP to support the new material
 
-
-## Non-Goals
-
-- Update all existing GEPs with relationships or other statuses. These will be
-  done later (for existing GEPs) or as they are created (for new GEPs).
-
 ## Introduction
 
 As part of preparing for work to split up GEP-713, we (the Gateway API and GAMMA
@@ -54,7 +48,7 @@ to what the KEP process uses, seems like it is increasingly necessary. This GEP
 introduces a schema, which will be detailed in `.go` files rather than completely
 in this document.
 
-Lastly, I think that we should clarify our use of [RFC2119](https://www.rfc-editor.org/rfc/rfc2119.txt)
+Lastly, we should clarify our use of [RFC2119](https://www.rfc-editor.org/rfc/rfc2119.txt)
 language - we use MUST, SHOULD, MAY and so on as per that RFC in general,
 but there is an extension in [RFC8174](https://www.rfc-editor.org/rfc/rfc8174.txt)
 that adds that these words are only to be interpreted per the RFC when they are
@@ -69,42 +63,12 @@ a _very_ good idea to adopt to me.
 RFC8174 clarifies that the reserved words MUST be in all-caps to have their
 assigned meaning. This should make the spec clearer over time as we migrate.
 
-### Addition of the concept of GEP "types", and a new GEP Type
-
-We will introduce the concept of GEP types.
-
-#### Types of GEP
-There will be two types of GEP. The existing type will be called `API` GEPs, and
-a new type `Memorandum` (after "Memorandum of Understanding") will be created.
-
-##### API GEPs
-
-GEPs that do not have an assigned type will be considered `API` GEPs. (For
-legacy GEPs). New GEPs created after this GEP is merged will default to the `API`
-type.
+### Addition of a new GEP status
 
-As they do currently, these GEPs lay out a problem the API needs to address,
-along with a rationale and a solution for that problem.
-
-This also uses the existing GEP process and phases:
-
-1. Discuss
-1. Provisional
-  1. (optional) Prototyping
-1. Implementable
-1. Experimental
-1. Standard
-1. Completed
-
-As part of the addition of relationships, we will extend these phases, but see
-the "Addition of GEP relationships" section for details, but in short, when an
-API GEP has been Obsoleted, it will be moved to a new "Obsolete" phase (which
-is functionally the same as "Declined").
-
-##### Memorandum GEPs
-
-These GEPs record an agreement on either the definition of a problem, its scope
+We will introduce a new GEP status, `Memorandum`, that marks a GEP as recording
+an agreement on either the definition of a problem, its scope
 and a common language, or further process changes to the GEP process itself.
+
 The defining characteristic here is that the GEP MUST NOT result in any changes
 to the Gateway API spec, and SHOULD result in further GEPs to further clarify.
 For GEPs that _do_ make changes to the API, but also require further GEPs to
@@ -114,10 +78,7 @@ Memorandum GEPs should be used sparingly, and should form the umbrella for a
 significant amount of work, particularly work that may have parts that can
 move through the GEP phases at different speeds.
 
-The process for Memorandum GEPs is much more simple, and has really only one
-main phase - "Accepted".
-
-This phase is reached when a Memorandum GEP is merged, although as we will document
+The status is reached when a Memorandum GEP is merged, although as we will document
 in the "Addition of GEP relationships" section, it can still be Updated
 or Obsoleted.
 
@@ -144,12 +105,11 @@ in this repository.
 With that said, here's a rough sample of what a GEPMetadata object will look like:
 
 ```yaml
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 2659
 name: Document and improve the GEP process
-type: Memorandum
-status: Accepted
+status: Memorandum
 relationships:
   # Normally, these will be omitted, because `omitempty`.
   # They are included here for clarity.
@@ -170,6 +130,12 @@ latestRelease: v1.1
 # references is a list of hyperlinks to relevant external references.
 # It's intended to be used for storing Github discussions, Google docs, etc.
 references: {}
+# featureNames is a list of the feature names introduced by the GEP, if there
+# are any. This will allow us to track which feature was introduced by which GEP.
+featureNames: {}
+# changelog is a list of hyperlinks to PRs that make changes to the GEP, in
+# ascending date order.
+changelog: {}
 ```
 
 ### Addition of GEP relationships

diff --git a/geps/gep-2659.yaml b/geps/gep-2659.yaml
@@ -1,20 +1,20 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 2659
 name: Document and improve the GEP process
 type: Memorandum
 status: Accepted
 relationships:
   seeAlso:
-  - number: 917
-    name: Gateway API Conformance Testing
-    description: GEP is Memorandum type
-  - number: 922
-    name: Gateway API Versioning
-    description: GEP is Memorandum type
-  - number: 1324
-    name: Service Mesh in Gateway API
-    description: GEP is Memorandum type
+    - number: 917
+      name: Gateway API Conformance Testing
+      description: GEP is Memorandum type
+    - number: 922
+      name: Gateway API Versioning
+      description: GEP is Memorandum type
+    - number: 1324
+      name: Service Mesh in Gateway API
+      description: GEP is Memorandum type
 authors:
   - youngnick
 latestRelease: v1.1
diff --git a/geps/gep-696.yaml b/geps/gep-696.yaml
@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha1
+apiVersion: internal.gateway.networking.k8s.io/v1alpha1
 kind: GEPDetails
 number: 696
 name: GEP template