From 12525051587af7eb1ba63a48ce1f138824ae1dc7 Mon Sep 17 00:00:00 2001 From: Skye Gill Date: Tue, 21 Mar 2023 10:51:31 +0000 Subject: [PATCH] namespace clarification Signed-off-by: Skye Gill --- OFEP-ofo-flagd-service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OFEP-ofo-flagd-service.md b/OFEP-ofo-flagd-service.md index fee5c8f..21e3ed1 100644 --- a/OFEP-ofo-flagd-service.md +++ b/OFEP-ofo-flagd-service.md @@ -11,7 +11,7 @@ The driving force behind this is to simplify the deployment of flagd for use by ## Proposal Introduce a FlagdService custom resource definition (CRD) and controller. -The controller uses the configuration defined within the custom resource (CR) to create a Service and a Deployment of flagd (backed by the Service) in the configured namespace. This is a common deployment pattern permitting access by any component that routes to the created Service (e.g. Ingress/Load Balancer). OFO already manages the [sidecar deployment pattern](https://learn.microsoft.com/en-us/azure/architecture/patterns/sidecar) to achieve the goal of internally routable flagd. In contrast, the described FlagdService pattern permits externally routable flagd. +The controller uses the configuration defined within the custom resource (CR) to create a Service and a Deployment of flagd (backed by the Service) in the same namespace as the CR. This is a common deployment pattern permitting access by any component that routes to the created Service (e.g. Ingress/Load Balancer). OFO already manages the [sidecar deployment pattern](https://learn.microsoft.com/en-us/azure/architecture/patterns/sidecar) to achieve the goal of internally routable flagd. In contrast, the described FlagdService pattern permits externally routable flagd. ### RBAC