## Description A detailed description of the Epic, including the business need, goals, and any relevant stakeholders. [P1BIGROCKS-2490](https://jira.il2.dso.mil/browse/P1BIGROCKS-2490) - Archived 23/12/29 Istio can be used to whitelist endpoints in the mesh by creating service entries for external URLs and only allowing approved (think AuthorizationPolicies) workloads from accessing the Services. This epic should enable the use of this easily within BigBang for particular packages that *may* require external connections (GitLab runners, ...?) This should also enable the use of a dedicated Istio Egress gateway for all communications, and an optional policy to enable: ```yaml spec: meshConfig: outboundTrafficPolicy: mode: REGISTRY_ONLY ``` that prevents objects in the mesh from talking to objects outside of the mesh ## Requirements/Scope A list of the high-level requirements that must be met for the Epic to be considered complete. The scope of the Epic, including any related initiatives, projects, or Epics. ## Out of Scope Work beyond the scope of this epic and potential follow ons etc.. ## Duration Expected time to completion. Ideally in # of weeks. ## Team - Service Mesh ## Epic Team Members - @stephen.galamb (Lead) - @sarnowski-unicorn - @cschaefer - @steven.donald - @w.griffing - @wyatt.fry ## Dependencies Any dependencies or prerequisites required for the completion of the Epic. ## Risks Any potential risks or obstacles that may impact the completion of the Epic. ## Acceptance Criteria A list of criteria that must be met for the Epic to be considered complete. Reference requirements if the same. ## Related Issues and/or Epics A list of related issues, such as stories or tasks, that will contribute to the completion of the Epic.