You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add gateway class label to generated objects (#3955)
This proposes adding an optional new label to generated objects. This is
useful for general querying, such as "find the total CPU usage of all
pods created by <implementation>".
Copy file name to clipboardExpand all lines: geps/gep-1762/index.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,7 @@ With this configuration, an implementation:
59
59
60
60
* MUST mark the Gateway as `Programmed` and provide an address in `Status.Addresses` where the Gateway can be reached on each configured port.
61
61
* MUST label all generated resources (Service, Deployment, etc) with `gateway.networking.k8s.io/gateway-name: my-gateway` (where `my-gateway` is the name of the Gateway resource).
62
+
* SHOULD label all generated resources (Service, Deployment, etc) with `gateway.networking.k8s.io/gateway-class-name: my-gateway-class` (where `my-gateway-class` is the name of the GatewayClass resource).
62
63
* MUST provision generated resources in the same namespace as the Gateway if they are namespace scoped resources.
63
64
* Cluster scoped resources are not recommended.
64
65
* SHOULD name all generated resources `my-gateway-example` (`<NAME>-<GATEWAY CLASS>`).
0 commit comments