From 89cf3429b90a8307d2698db64f086063d39b0375 Mon Sep 17 00:00:00 2001 From: alex Date: Wed, 13 Apr 2022 14:45:00 -0400 Subject: [PATCH 01/14] Adds initial goals doc Signed-off-by: alex --- GOALS.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 GOALS.md diff --git a/GOALS.md b/GOALS.md new file mode 100644 index 0000000000..d6b0b1d661 --- /dev/null +++ b/GOALS.md @@ -0,0 +1,5 @@ +# Goals + +WIP and comments on the project's goals can currently be found in this document: +https://docs.google.com/document/d/18MuuV9Qzij7Z1OeZ6GrOURKzVi9D0qv2SgvFPELM4gc/edit + From 6b492ac872b00fc56622fa6b69dd03b0dca35e64 Mon Sep 17 00:00:00 2001 From: alex Date: Mon, 18 Apr 2022 10:53:36 -1000 Subject: [PATCH 02/14] Populates content from the google docs, comments and discussions into the markdown file Signed-off-by: alex --- GOALS.md | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 67 insertions(+), 1 deletion(-) diff --git a/GOALS.md b/GOALS.md index d6b0b1d661..cb437e3112 100644 --- a/GOALS.md +++ b/GOALS.md @@ -1,5 +1,71 @@ # Goals -WIP and comments on the project's goals can currently be found in this document: +The high-level goal of the Envoy Gateway project is to attract more users to Envoy by adding new capabilities +and lowering barriers to adoption. + +## Objectives + +### Simplified and expressive API +The Envoy Gateway project will introduce a simplified API, with defaults set for many capabilities. + +This simplified API will make Envoy accessible to more users, especially application developers, and make Envoy a +stronger option for "getting started" as compared to Nginx/HAProxy. Application developers will use this simple API +out of the box without needing to understand in-depth concepts of Envoy Proxy or use OSS wrappers. +The simplified API will use nouns that application developers understand. + +The core full-featured Envoy APIs (xDS) will remain available for those who need more capability and for those who +add functionality on top of Envoy, such as commercial API gateway products. + +This simplified API will not be implemented by the Envoy Proxy, but rather an officially supported translation layer +on top. + +### All environments +The Envoy Gateway will support running natively in Kubernetes environments as well as non-Kubernetes deployments. + +Initially, Kubernetes will receive the most focus, with the aim of having the Envoy Gateway become the de facto +standard for Kubernetes ingress supporting the [Gateway API](https://gateway-api.sigs.k8s.io/). +Medium-term goals include multi-cluster support and various runtime environments. + +### Extensibility +Vendors will have the ability to provide value-added products built on the Envoy Gateway foundation. + +It will remain easy for end-users to use common Envoy Proxy extension points such as providing an implementation for +authentication methods and rate-limiting. For advanced use cases, users will have the ability to switch to using xDS +directly. + +Since a general-purpose API cannot address all use cases, the Envoy Gateway will provide additional extension points +for flexibility. As such, the Envoy Gateway will form the base of vendor-provided managed control plane solutions, +allowing vendors to shift to a higher management plane layer. + +## Non-objectives + +### Cannibalize vendor models +Vendors need to have the ability to add value and make money, so the goal is not to cannibalize any existing vendor +monetization model, though some vendors may be affected by it. + +### Disrupt current Envoy usage patterns +The Envoy Gateway is purely an additive convenience layer and is not meant to disrupt any usage pattern of any user +with Envoy Proxy, xDS, or go-control-plane. + +## Personas +_In order of priority_ + +### 1. Application developer +The application developer spends the majority of their time developing business logic code. They require API gateway +functionalities to expose their applications. Using expressive configurations, they will define request routes, +TLS termination, rate limits, authentication and authorization policies, etc. + +### 2. Infrastructure administrators +The infrastructure administrators are responsible for the installation, maintenance, and operation of +API gateways appliances in infrastructure, such as CRDs, roles, service accounts, certificates, etc. +Infrastructure administrators support the needs of application developers by deploying instances of the Envoy Gateway. + +### 3. Envoy developer +The Envoy developer has the ability to quickly develop and test out new or improved features in Envoy proxy, +that later can be graduated into a user-friendly gateway feature. + +## Other + +Further discussions and drafts of the project's goals can be found in this document: https://docs.google.com/document/d/18MuuV9Qzij7Z1OeZ6GrOURKzVi9D0qv2SgvFPELM4gc/edit From 4884ca30045707262114c753a9fa4c7ec1855b7d Mon Sep 17 00:00:00 2001 From: Alex Gervais Date: Tue, 19 Apr 2022 07:04:11 -1000 Subject: [PATCH 03/14] Update GOALS.md Co-authored-by: Arko Dasgupta Signed-off-by: alex --- GOALS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOALS.md b/GOALS.md index cb437e3112..7a384beb96 100644 --- a/GOALS.md +++ b/GOALS.md @@ -40,7 +40,7 @@ allowing vendors to shift to a higher management plane layer. ## Non-objectives ### Cannibalize vendor models -Vendors need to have the ability to add value and make money, so the goal is not to cannibalize any existing vendor +Vendors need to have the ability to drive commercial value, so the goal is not to cannibalize any existing vendor monetization model, though some vendors may be affected by it. ### Disrupt current Envoy usage patterns From 77651b56f0290a425fb04ea9451769015357a95b Mon Sep 17 00:00:00 2001 From: alex Date: Thu, 21 Apr 2022 06:31:10 -1000 Subject: [PATCH 04/14] Splits the goals into "Expressive API" and "Simplified deployment" Signed-off-by: alex --- GOALS.md | 27 ++++++++++++++++++--------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/GOALS.md b/GOALS.md index 7a384beb96..20a58c0a68 100644 --- a/GOALS.md +++ b/GOALS.md @@ -1,30 +1,39 @@ # Goals -The high-level goal of the Envoy Gateway project is to attract more users to Envoy by adding new capabilities -and lowering barriers to adoption. +The high-level goal of the Envoy Gateway project is to attract more users to Envoy by lowering barriers to adoption +through expressive, extensible, role-oriented APIs that support a multitude of ingress and L7/L4 traffic routing +use cases. ## Objectives -### Simplified and expressive API -The Envoy Gateway project will introduce a simplified API, with defaults set for many capabilities. +### Expressive API +The Envoy Gateway project will expose a simplified and expressive API, with defaults set for many capabilities. -This simplified API will make Envoy accessible to more users, especially application developers, and make Envoy a -stronger option for "getting started" as compared to Nginx/HAProxy. Application developers will use this simple API +This expressive API will make Envoy accessible to more users, especially application developers, and make Envoy a +stronger option for "getting started" as compared to other proxies. Application developers will use a simple API out of the box without needing to understand in-depth concepts of Envoy Proxy or use OSS wrappers. -The simplified API will use nouns that application developers understand. +The expressive API will use familiar nouns that [expert personas](#personas) understand. The core full-featured Envoy APIs (xDS) will remain available for those who need more capability and for those who add functionality on top of Envoy, such as commercial API gateway products. -This simplified API will not be implemented by the Envoy Proxy, but rather an officially supported translation layer +This expressive API will not be implemented by the Envoy Proxy, but rather an officially supported translation layer on top. +### Simplified deployment +The Envoy Gateway will simplify how Envoy is deployed and managed, allowing application developers to focus on +delivering core business value. + +Making an application accessible needs to be a trivial task for any developer. Similarly, infrastructure administrator +will enjoy a simplified deployment model that doesn't require extensive knowledge of the solution's architecture to +operate. + ### All environments The Envoy Gateway will support running natively in Kubernetes environments as well as non-Kubernetes deployments. Initially, Kubernetes will receive the most focus, with the aim of having the Envoy Gateway become the de facto standard for Kubernetes ingress supporting the [Gateway API](https://gateway-api.sigs.k8s.io/). -Medium-term goals include multi-cluster support and various runtime environments. +Additional goals include multi-cluster support and various runtime environments. ### Extensibility Vendors will have the ability to provide value-added products built on the Envoy Gateway foundation. From 12d39a52886c60b8df197b9c52b66ccf72aeca42 Mon Sep 17 00:00:00 2001 From: alex Date: Fri, 22 Apr 2022 10:33:53 -1000 Subject: [PATCH 05/14] Revised personas, direct xDS references and misc wording Signed-off-by: alex --- GOALS.md | 24 +++++++----------------- 1 file changed, 7 insertions(+), 17 deletions(-) diff --git a/GOALS.md b/GOALS.md index 20a58c0a68..30c7bc9623 100644 --- a/GOALS.md +++ b/GOALS.md @@ -12,9 +12,9 @@ The Envoy Gateway project will expose a simplified and expressive API, with defa This expressive API will make Envoy accessible to more users, especially application developers, and make Envoy a stronger option for "getting started" as compared to other proxies. Application developers will use a simple API out of the box without needing to understand in-depth concepts of Envoy Proxy or use OSS wrappers. -The expressive API will use familiar nouns that [expert personas](#personas) understand. +The expressive API will use familiar nouns that [users](#personas) understand. -The core full-featured Envoy APIs (xDS) will remain available for those who need more capability and for those who +The core full-featured Envoy APIs will remain available for those who need more capability and for those who add functionality on top of Envoy, such as commercial API gateway products. This expressive API will not be implemented by the Envoy Proxy, but rather an officially supported translation layer @@ -24,8 +24,8 @@ on top. The Envoy Gateway will simplify how Envoy is deployed and managed, allowing application developers to focus on delivering core business value. -Making an application accessible needs to be a trivial task for any developer. Similarly, infrastructure administrator -will enjoy a simplified deployment model that doesn't require extensive knowledge of the solution's architecture to +Making an application accessible needs to be a trivial task for any developer. Similarly, infrastructure administrators +will enjoy a simplified management model that doesn't require extensive knowledge of the solution's architecture to operate. ### All environments @@ -39,8 +39,8 @@ Additional goals include multi-cluster support and various runtime environments. Vendors will have the ability to provide value-added products built on the Envoy Gateway foundation. It will remain easy for end-users to use common Envoy Proxy extension points such as providing an implementation for -authentication methods and rate-limiting. For advanced use cases, users will have the ability to switch to using xDS -directly. +authentication methods and rate-limiting. For advanced use cases, users will have the ability to use the full power +of xDS. Since a general-purpose API cannot address all use cases, the Envoy Gateway will provide additional extension points for flexibility. As such, the Envoy Gateway will form the base of vendor-provided managed control plane solutions, @@ -67,14 +67,4 @@ TLS termination, rate limits, authentication and authorization policies, etc. ### 2. Infrastructure administrators The infrastructure administrators are responsible for the installation, maintenance, and operation of API gateways appliances in infrastructure, such as CRDs, roles, service accounts, certificates, etc. -Infrastructure administrators support the needs of application developers by deploying instances of the Envoy Gateway. - -### 3. Envoy developer -The Envoy developer has the ability to quickly develop and test out new or improved features in Envoy proxy, -that later can be graduated into a user-friendly gateway feature. - -## Other - -Further discussions and drafts of the project's goals can be found in this document: -https://docs.google.com/document/d/18MuuV9Qzij7Z1OeZ6GrOURKzVi9D0qv2SgvFPELM4gc/edit - +Infrastructure administrators support the needs of application developers by managing instances of the Envoy Gateway. From 9fd29b13aeafe82977378cc7706b0d44a20c4049 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Wed, 27 Apr 2022 14:47:30 -0600 Subject: [PATCH 06/14] =?UTF-8?q?GOALS:=20"the=20Envoy=20Gateway"=20?= =?UTF-8?q?=E2=86=92=20"Envoy=20Gateway"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Luke Shumaker --- GOALS.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/GOALS.md b/GOALS.md index 30c7bc9623..24eb8a720a 100644 --- a/GOALS.md +++ b/GOALS.md @@ -21,7 +21,7 @@ This expressive API will not be implemented by the Envoy Proxy, but rather an of on top. ### Simplified deployment -The Envoy Gateway will simplify how Envoy is deployed and managed, allowing application developers to focus on +Envoy Gateway will simplify how Envoy is deployed and managed, allowing application developers to focus on delivering core business value. Making an application accessible needs to be a trivial task for any developer. Similarly, infrastructure administrators @@ -29,9 +29,9 @@ will enjoy a simplified management model that doesn't require extensive knowledg operate. ### All environments -The Envoy Gateway will support running natively in Kubernetes environments as well as non-Kubernetes deployments. +Envoy Gateway will support running natively in Kubernetes environments as well as non-Kubernetes deployments. -Initially, Kubernetes will receive the most focus, with the aim of having the Envoy Gateway become the de facto +Initially, Kubernetes will receive the most focus, with the aim of having Envoy Gateway become the de facto standard for Kubernetes ingress supporting the [Gateway API](https://gateway-api.sigs.k8s.io/). Additional goals include multi-cluster support and various runtime environments. @@ -42,8 +42,8 @@ It will remain easy for end-users to use common Envoy Proxy extension points suc authentication methods and rate-limiting. For advanced use cases, users will have the ability to use the full power of xDS. -Since a general-purpose API cannot address all use cases, the Envoy Gateway will provide additional extension points -for flexibility. As such, the Envoy Gateway will form the base of vendor-provided managed control plane solutions, +Since a general-purpose API cannot address all use cases, Envoy Gateway will provide additional extension points +for flexibility. As such, Envoy Gateway will form the base of vendor-provided managed control plane solutions, allowing vendors to shift to a higher management plane layer. ## Non-objectives @@ -53,7 +53,7 @@ Vendors need to have the ability to drive commercial value, so the goal is not t monetization model, though some vendors may be affected by it. ### Disrupt current Envoy usage patterns -The Envoy Gateway is purely an additive convenience layer and is not meant to disrupt any usage pattern of any user +Envoy Gateway is purely an additive convenience layer and is not meant to disrupt any usage pattern of any user with Envoy Proxy, xDS, or go-control-plane. ## Personas @@ -67,4 +67,4 @@ TLS termination, rate limits, authentication and authorization policies, etc. ### 2. Infrastructure administrators The infrastructure administrators are responsible for the installation, maintenance, and operation of API gateways appliances in infrastructure, such as CRDs, roles, service accounts, certificates, etc. -Infrastructure administrators support the needs of application developers by managing instances of the Envoy Gateway. +Infrastructure administrators support the needs of application developers by managing instances of Envoy Gateway. From e7dd2dd2abca0f2066c4135c7e2ee27c4f3a2d65 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Wed, 27 Apr 2022 14:47:56 -0600 Subject: [PATCH 07/14] =?UTF-8?q?GOALS:=20"the=20Envoy=20Proxy"=20?= =?UTF-8?q?=E2=86=92=20"Envoy=20Proxy"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Luke Shumaker --- GOALS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOALS.md b/GOALS.md index 24eb8a720a..a0e19b32fb 100644 --- a/GOALS.md +++ b/GOALS.md @@ -17,7 +17,7 @@ The expressive API will use familiar nouns that [users](#personas) understand. The core full-featured Envoy APIs will remain available for those who need more capability and for those who add functionality on top of Envoy, such as commercial API gateway products. -This expressive API will not be implemented by the Envoy Proxy, but rather an officially supported translation layer +This expressive API will not be implemented by Envoy Proxy, but rather an officially supported translation layer on top. ### Simplified deployment From c721087d7a08f068ac47caf527eef3d1fcec0644 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Wed, 27 Apr 2022 15:08:49 -0600 Subject: [PATCH 08/14] GOALS: Fuss with wording for readability Signed-off-by: Luke Shumaker --- GOALS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/GOALS.md b/GOALS.md index a0e19b32fb..e2e93f8631 100644 --- a/GOALS.md +++ b/GOALS.md @@ -38,8 +38,8 @@ Additional goals include multi-cluster support and various runtime environments. ### Extensibility Vendors will have the ability to provide value-added products built on the Envoy Gateway foundation. -It will remain easy for end-users to use common Envoy Proxy extension points such as providing an implementation for -authentication methods and rate-limiting. For advanced use cases, users will have the ability to use the full power +It will remain easy for end-users to leverage common Envoy Proxy extension points such as providing an implementation +for authentication methods and rate-limiting. For advanced use cases, users will have the ability to use the full power of xDS. Since a general-purpose API cannot address all use cases, Envoy Gateway will provide additional extension points From e21312abc0d7401d270c21027ab3067abcfcb9e8 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Wed, 27 Apr 2022 15:12:57 -0600 Subject: [PATCH 09/14] GOALS: Simplify the app-dev persona This is the description suggested by Daneyon on GH, but with the phrase ", e.g. path-based routing" removed per Alex and Nick. Co-authored-by: danehans Signed-off-by: Luke Shumaker --- GOALS.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/GOALS.md b/GOALS.md index e2e93f8631..07e68540a9 100644 --- a/GOALS.md +++ b/GOALS.md @@ -60,9 +60,8 @@ with Envoy Proxy, xDS, or go-control-plane. _In order of priority_ ### 1. Application developer -The application developer spends the majority of their time developing business logic code. They require API gateway -functionalities to expose their applications. Using expressive configurations, they will define request routes, -TLS termination, rate limits, authentication and authorization policies, etc. +The application developer spends the majority of their time developing business logic code. They require the ability to +manage access to their application. ### 2. Infrastructure administrators The infrastructure administrators are responsible for the installation, maintenance, and operation of From 8792c733352735b5c50072af94fc6e17583e7c18 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Wed, 27 Apr 2022 15:44:13 -0600 Subject: [PATCH 10/14] GOALS: Try to better highlight that it's Gateway API Signed-off-by: Luke Shumaker --- GOALS.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/GOALS.md b/GOALS.md index 07e68540a9..a13899c388 100644 --- a/GOALS.md +++ b/GOALS.md @@ -7,12 +7,13 @@ use cases. ## Objectives ### Expressive API -The Envoy Gateway project will expose a simplified and expressive API, with defaults set for many capabilities. +The Envoy Gateway project will expose a simple and expressive API, with defaults set for many capabilities. -This expressive API will make Envoy accessible to more users, especially application developers, and make Envoy a -stronger option for "getting started" as compared to other proxies. Application developers will use a simple API -out of the box without needing to understand in-depth concepts of Envoy Proxy or use OSS wrappers. -The expressive API will use familiar nouns that [users](#personas) understand. +The API is the Kubernetes-native [Gateway API][], plus Envoy-specific extensions and extension points. This expressive +and familiar API will make Envoy accessible to more users, especially application developers, and make Envoy a stronger +option for "getting started" as compared to other proxies. Application developers will use a simple API out of the box +without needing to understand in-depth concepts of Envoy Proxy or use OSS wrappers. The expressive API will use +familiar nouns that [users](#personas) understand. The core full-featured Envoy APIs will remain available for those who need more capability and for those who add functionality on top of Envoy, such as commercial API gateway products. @@ -32,7 +33,7 @@ operate. Envoy Gateway will support running natively in Kubernetes environments as well as non-Kubernetes deployments. Initially, Kubernetes will receive the most focus, with the aim of having Envoy Gateway become the de facto -standard for Kubernetes ingress supporting the [Gateway API](https://gateway-api.sigs.k8s.io/). +standard for Kubernetes ingress supporting the [Gateway API][]. Additional goals include multi-cluster support and various runtime environments. ### Extensibility @@ -67,3 +68,5 @@ manage access to their application. The infrastructure administrators are responsible for the installation, maintenance, and operation of API gateways appliances in infrastructure, such as CRDs, roles, service accounts, certificates, etc. Infrastructure administrators support the needs of application developers by managing instances of Envoy Gateway. + +[Gateway API]: https://gateway-api.sigs.k8s.io/ From 5172fcc30f1d4adcd32a31a1f71dfd5e622c4a08 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Wed, 27 Apr 2022 15:49:57 -0600 Subject: [PATCH 11/14] GOALS: Use just "the API" rather than "the [adjective] API" for readability Signed-off-by: Luke Shumaker --- GOALS.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/GOALS.md b/GOALS.md index a13899c388..5cd72a8b80 100644 --- a/GOALS.md +++ b/GOALS.md @@ -9,11 +9,11 @@ use cases. ### Expressive API The Envoy Gateway project will expose a simple and expressive API, with defaults set for many capabilities. -The API is the Kubernetes-native [Gateway API][], plus Envoy-specific extensions and extension points. This expressive -and familiar API will make Envoy accessible to more users, especially application developers, and make Envoy a stronger -option for "getting started" as compared to other proxies. Application developers will use a simple API out of the box -without needing to understand in-depth concepts of Envoy Proxy or use OSS wrappers. The expressive API will use -familiar nouns that [users](#personas) understand. +The API will be the Kubernetes-native [Gateway API][], plus Envoy-specific extensions and extension points. This +expressive and familiar API will make Envoy accessible to more users, especially application developers, and make Envoy +a stronger option for "getting started" as compared to other proxies. Application developers will use the API out of +the box without needing to understand in-depth concepts of Envoy Proxy or use OSS wrappers. The API will use familiar +nouns that [users](#personas) understand. The core full-featured Envoy APIs will remain available for those who need more capability and for those who add functionality on top of Envoy, such as commercial API gateway products. From eb0db71bce7a984a23f991812e6bf31e4281747a Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Wed, 27 Apr 2022 15:55:38 -0600 Subject: [PATCH 12/14] GOALS: Mention vendor-extensibility in the intro paragraph Signed-off-by: Luke Shumaker --- GOALS.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/GOALS.md b/GOALS.md index 5cd72a8b80..c99b798ea9 100644 --- a/GOALS.md +++ b/GOALS.md @@ -2,7 +2,8 @@ The high-level goal of the Envoy Gateway project is to attract more users to Envoy by lowering barriers to adoption through expressive, extensible, role-oriented APIs that support a multitude of ingress and L7/L4 traffic routing -use cases. +use cases; and provide a common foundation for vendors to build value-added products without having to re-engineer +fundamental interactions. ## Objectives From bd5bc15fb5ce1375d0e2dca207f5a6b3835ea9a2 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Wed, 27 Apr 2022 16:07:14 -0600 Subject: [PATCH 13/14] GOALS: Have a go at "batteries included" Signed-off-by: Luke Shumaker --- GOALS.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/GOALS.md b/GOALS.md index c99b798ea9..c752ba44f7 100644 --- a/GOALS.md +++ b/GOALS.md @@ -22,10 +22,16 @@ add functionality on top of Envoy, such as commercial API gateway products. This expressive API will not be implemented by Envoy Proxy, but rather an officially supported translation layer on top. -### Simplified deployment +### Batteries included Envoy Gateway will simplify how Envoy is deployed and managed, allowing application developers to focus on delivering core business value. +The project plans to include additional infrastructure components required by users to fulfill their Ingress and API +gateway needs: It will handle Envoy infrastructure provisioning (e.g. Kubernetes Service, Deployment, et cetera), and +possibly infrastructure provisioning of related sidecar services. It will include sensible defaults with the ability to +override. It will included channels for improving ops by exposing status through API conditions and Kubernetes status +sub-resources. + Making an application accessible needs to be a trivial task for any developer. Similarly, infrastructure administrators will enjoy a simplified management model that doesn't require extensive knowledge of the solution's architecture to operate. From f0d486f030cbc1c0a598adc804c894333104665c Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Thu, 28 Apr 2022 09:23:11 -0600 Subject: [PATCH 14/14] GOALS: Fix a sentence with mixed tense Co-authored-by: Arko Dasgupta --- GOALS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOALS.md b/GOALS.md index c752ba44f7..bf93630f06 100644 --- a/GOALS.md +++ b/GOALS.md @@ -29,7 +29,7 @@ delivering core business value. The project plans to include additional infrastructure components required by users to fulfill their Ingress and API gateway needs: It will handle Envoy infrastructure provisioning (e.g. Kubernetes Service, Deployment, et cetera), and possibly infrastructure provisioning of related sidecar services. It will include sensible defaults with the ability to -override. It will included channels for improving ops by exposing status through API conditions and Kubernetes status +override. It will include channels for improving ops by exposing status through API conditions and Kubernetes status sub-resources. Making an application accessible needs to be a trivial task for any developer. Similarly, infrastructure administrators