Skip to content

Commit 5c49ed4

Browse files
Update gep-1856.md
To resolve suggestion to change from "a resource" to "an endpoint" from @shaneutt
1 parent 8ad2040 commit 5c49ed4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

geps/gep-1856.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Issue: [#1856](https://github.com/kubernetes-sigs/gateway-api/issues/1856)
44
Status: Provisional
55

66
## TLDR
7-
Egress traffic is any traffic that originates inside a Kubernetes cluster that is bound for a resource outside of the cluster. Egress Traffic in Kubernetes is a common use case for Service Providers to provision outbound traffic that requires a Gateway resource to provide Source Network Address Translation (SNAT) capabilities.
7+
Egress traffic is any traffic that originates inside a Kubernetes cluster that is bound for an endpoint outside of the cluster. Egress Traffic in Kubernetes is a common use case for Service Providers to provision outbound traffic that requires a Gateway resource to provide Source Network Address Translation (SNAT) capabilities.
88

99
This GEP intends to provide formal rules for how an application can reach an endpoint outside of the cluster via a Gateway. The egress path is protocol agnostic and the Gateway can be connected to multiple external networks.
1010

0 commit comments

Comments
 (0)