chore: architecture diagrams

.codespellrc

@@ -1,6 +1,6 @@
 # Lint Codespell configurations
 [codespell]
-skip = .codespellrc,.git,node_modules,build,dist,*.zst,CHANGELOG.md,.playwright,.terraform
+skip = .codespellrc,.git,node_modules,build,dist,*.zst,CHANGELOG.md,.playwright,.terraform,*.svg
 ignore-words-list = NotIn,AKS,LICENS,aks,afterAll
 enable-colors =
 check-hidden =

.github/workflows/pull-request-conditionals.yaml

@@ -19,6 +19,7 @@ on:
       - .gitignore
       - renovate.json
       - .release-please-config.json
+      - .codespellrc
       - release-please-config.json
       - CODEOWNERS
       - LICENSE

docs/reference/UDS Core/overview.md

@@ -14,6 +14,8 @@ UDS Core enables your team to:
 - Leverage specific functional applications to deliver a versatile platform that caters to diverse mission objectives.
 - Enhance the efficiency, security, and success of software delivery and operations process.
 
+![UDS Core Architecture Diagram](https://github.com/defenseunicorns/uds-core/blob/main/docs/.images/uds-core-arch-overview.svg?raw=true)
+
 ### Accomplishing Mission Objectives with Functional Applications
 
 UDS leverages functional applications that are well-suited to perform the specific tasks required. These tools are carefully selected to ensure optimal performance and compatibility within the UDS landscape. By integrating functional tools into the platform, UDS ensures that Mission Heroes have access to cutting-edge technologies and best-in-class solutions for their missions.

docs/reference/configuration/ingress.md

@@ -4,6 +4,8 @@ title: Istio Ingress
 
 UDS Core leverages Istio for ingress into the service mesh. This document provides an overview and examples of the Istio resources that UDS Core deploys to handle ingress.
 
+![UDS Core Ingress / Egress](https://github.com/defenseunicorns/uds-core/blob/main/docs/.images/uds-core-arch-ports-protocols.svg?raw=true)
+
 ## Gateways
 
 UDS Core provides a few Istio [Gateway](https://istio.io/latest/docs/reference/config/networking/gateway/) resources to allow ingress into the service mesh. Each one serves a different purpose and can be used to route traffic to different services.