-
Notifications
You must be signed in to change notification settings - Fork 94
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Previously, NKG used the cluster IP of the Service to route traffic to the backend Services specified by HTTPRoutes. With this commit, NKG will use the endpoints of the Pods corresponding to a Service as the upstream servers for a backend Service. This change adds the following components: * EndpointSlice controller for caching and listing EndpointSlices. * Relationship.Capturer for tracking and reporting on relationships between Gateway API resources and non-Gateway API resources (e.g. Services). * ServiceResolver replaces the ServiceStore and resolves Service:Port to a list * of endpoints. This commit also adds upstreams to the nginx config generator. One upstream is generated for each unique and valid Service:Port BackendRef. If a BackendRef cannot be resolved, a 502 is returned. Known Limitations: * Traffic cannot be routed to Headless Services that do not have a defined port. * If a user manually creates and EndpointSlice, they will need to populate the "kubernetes.io/service-name" label and set the ready condition of the endpoints to true. Otherwise, NKG will fail to resolve the Service endpoints.
- Loading branch information
1 parent
b946e9c
commit 231937f
Showing
53 changed files
with
4,783 additions
and
1,445 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.