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
> Gloo Gateway is now a fully conformant Kubernetes Gateway API implementation!
13
13
>
14
-
> The existing Gloo Edge v1 APIs were not changed and continue to be fully supported.
14
+
> The existing Gloo Edge APIs were not changed and continue to be fully supported.
15
15
16
16
## About Gloo Gateway
17
17
Gloo Gateway is a powerful Kubernetes-native ingress controller and API gateway that is based on the Kubernetes Gateway API. It excels in function-level routing, supports legacy apps, microservices and serverless, offers robust discovery capabilities, integrates seamlessly with open-source projects, and is designed to support hybrid applications with various technologies, architectures, protocols, and clouds.
-**Kubernetes Gateway API**: Gloo Gateway is a feature-rich ingress controller, built on top of the Envoy Proxy and fully conformant with the Kubernetes Gateway API.
@@ -113,14 +43,14 @@ C) Allow different teams in an organization choose different architectures. See
113
43
## Next Steps
114
44
- Join us on our Slack channel: [https://slack.solo.io/](https://slack.solo.io/)
115
45
- Follow us on Twitter: [https://twitter.com/soloio_inc](https://twitter.com/soloio_inc)
116
-
- Check out the docs: [https://docs.solo.io/gloo-gateway/v2](https://docs.solo.io/gloo-gateway/v2)
117
-
- Check out the code and contribute: [Contribution Guides](/devel/contributing)
46
+
- Check out the docs: [https://docs.solo.io/gateway/latest/](https://docs.solo.io/gateway/latest/)
118
47
119
-
## Thanks
48
+
## Contributing to Gloo Gateway
49
+
The [devel](devel) folder should be the starting point for understanding the code, and contributing to the product.
120
50
51
+
## Thanks
121
52
**Gloo Gateway** would not be possible without the valuable open-source work of projects in the community. We would like to extend a special thank-you to [Envoy](https://www.envoyproxy.io).
122
53
123
54
124
55
## Security
125
-
126
56
*Reporting security issues* : We take Gloo Gateway's security very seriously. If you've found a security issue or a potential security issue in Gloo Gateway, please DO NOT file a public Github issue, instead send your report privately to [security@solo.io](mailto:security@solo.io).
Find tools and information to help you develop the Gloo Edge project.
3
+
Find tools and information to help you develop the Gloo Gateway project.
4
4
5
+
*`architecture`: Descriptions about high-level design and implementation details of various packages and features.
5
6
*`contributing`: Information to help you contribute to the project, such as how to open issues, review pull requests, generate code, and backport fixes.
6
7
*`debugging`: Troubleshooting steps for debugging frequent issues.
7
8
*`testing`: Descriptions on how the tests work and how to use them.
8
-
*`tools`: A set of scripts and tools that are intended to help you develop the Gloo Edge project's codebase. Learn more about these tools in the short descriptions later in this readme.
9
-
10
-
_**Note**: For tools that help maintain an installation of Gloo Edge (the product, not the project codebase), build those tools into the [CLI](/projects/gloo/cli) instead._
9
+
*`tools`: A set of scripts and tools that are intended to help you develop the Gloo Gateway project's codebase. Learn more about these tools in the short descriptions later in this readme.
11
10
12
11
Other resources:
13
-
*[Developer guide](https://docs.solo.io/gloo-edge/latest/guides/dev/) to set up your development environment and learn more about extending the functionality of the Gloo Edge project and related plug-ins. While written for external contributors, internal Solo developers might also find this guide helpful when onboarding.
14
-
*[Product documentation](https://docs.solo.io/gloo-edge/latest/) with guides for end users to use Gloo Edge as a product
12
+
*[Developer guide](https://docs.solo.io/gloo-edge/latest/guides/dev/) to set up your development environment and learn more about extending the functionality of the Gloo Gateway project and related plug-ins. While written for external contributors, internal Solo developers might also find this guide helpful when onboarding.
13
+
*[Product documentation](https://docs.solo.io/gloo-edge/latest/) with guides for end users to use Gloo Gateway as a product
15
14
*[Guide to contribute to the documentation](https://docs.solo.io/gloo-edge/latest/contributing/documentation/)
Copy file name to clipboardExpand all lines: devel/architecture/endpoint-discovery.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
# Endpoint Discovery Service (EDS)
2
2
3
3
## Overview
4
-
Envoy supports a variety of mechanisms to configure [Service Discovery](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/service_discovery#arch-overview-service-discovery), the mechanism Envoy uses to resolve the members of the cluster. One of the more complex mechanisms is [EDS](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/service_discovery#endpoint-discovery-service-eds), where the xDS management server (Gloo Edge) provides the Endpoints for a given Cluster via an API.
4
+
Envoy supports a variety of mechanisms to configure [Service Discovery](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/service_discovery#arch-overview-service-discovery), the mechanism Envoy uses to resolve the members of the cluster. One of the more complex mechanisms is [EDS](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/service_discovery#endpoint-discovery-service-eds), where the xDS management server (Gloo Gateway) provides the Endpoints for a given Cluster via an API.
5
5
6
-
In Gloo Edge, Endpoints can be discovered dynamically via the Endpoint Discovery feature, and then served to the Envoy proxy via the EDS API.
6
+
In Gloo Gateway, Endpoints can be discovered dynamically via the Endpoint Discovery feature, and then served to the Envoy proxy via the EDS API.
7
7
8
8
## How it works
9
-
EDS runs in the [Gloo](/projects/gloo) component of Gloo Edge.
9
+
EDS runs in the [Gloo](/projects/gloo) component of Gloo Gateway.
10
10
11
11
We rely on an [In Memory Endpoint Client](https://github.com/solo-io/gloo/blob/a39fb91c2fb122d5a34353dff891e0b0044bf1dc/projects/gloo/pkg/syncer/setup/setup_syncer.go#L469), meaning that when we “write” an Endpoint, it is just persisted in memory. In Memory clients signal updates to the emitter by two mechanisms:
Copy file name to clipboardExpand all lines: devel/architecture/external-options.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# External Options (VirtualHostOption and RouteOption)
2
2
3
3
## Overview
4
-
Gloo Edge supports decoupling certain resources from the definitions of options related to the resource. Currently there are two objects which support delegating options definition in this way:
4
+
Gloo Gateway supports decoupling certain resources from the definitions of options related to the resource. Currently there are two objects which support delegating options definition in this way:
5
5
- A VirtualHost (exists on a VirtualService) can be configured with the separate resource [VirtualHostOption](./projects/gateway/api/v1/external_options.proto).
6
6
- A Route (exists on a VirtualHost within a VirtualService or on a RouteTable) can be configured with the separate resource [RouteOption](./projects/gateway/api/v1/external_options.proto).
Copy file name to clipboardExpand all lines: devel/architecture/static_metadata.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ The [Gloo Proxy Api](https://docs.solo.io/gloo-edge/latest/reference/api/github.
8
8
9
9
This metadata is not required and the `resourceKind`, `resourceRef.name`, and `resourceRef.namespace` fields which compose the metadata are plain strings.
10
10
11
-
While the objects used to create the Proxy Api resources are and should be generally irrelevant to the functionality of Gloo Edge, they do provide user facing value as sources of names and labels.
11
+
While the objects used to create the Proxy Api resources are and should be generally irrelevant to the functionality of Gloo Gateway, they do provide user facing value as sources of names and labels.
Copy file name to clipboardExpand all lines: devel/architecture/upstream-discovery.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -3,10 +3,10 @@
3
3
## Overview
4
4
A [Gloo Upstream](/projects/gloo/api/v1/upstream.proto) represents a destination for routing HTTP requests. An Upstream can be compared to [clusters](https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/cluster/v3/cluster.proto) in Envoy terminology.
5
5
6
-
Upstreams can either be defined statically in a cluster, or can be discovered dynamically via Gloo Edge's Upstream Discovery feature.
6
+
Upstreams can either be defined statically in a cluster, or can be discovered dynamically via Gloo Gateway's Upstream Discovery feature.
7
7
8
8
## How it works
9
-
UDS runs in the [Discovery](/projects/discovery) component of Gloo Edge.
9
+
UDS runs in the [Discovery](/projects/discovery) component of Gloo Gateway.
10
10
11
11
Create a [discovery emitter](https://github.com/solo-io/gloo/blob/8bbe175ea136178bfe8b4d103ae702d4965c4c75/projects/gloo/pkg/api/v1/discovery_snapshot_emitter.sk.go#L135), which is responsible for the following:
12
12
- Emit a snapshot of the resources that are required for UDS to operate (Upstreams, Secrets, Kubernetes Namespaces)
![soloio-bulldozer[bot]](https://avatars.githubusercontent.com/in/26741?v=4&size=40){kind=avatar}
0 commit comments