https://samplayskeys.github.io/Workspace/architecture/index.htmlThis section compiles primary system architecture blueprints, integration designs, and infrastructure roadmaps. Architecture Blueprints Security & Integrations Tailscale Integration for OpenBao - Security architecture for generating secure, on-demand Tailscale authorization keys for Dockerized containers using HashiCorp Vault / OpenBao. Deployment Orchestration BigFix Discovery & Server Deployment - Architectural design for rolling out BigFix server and discovery engines inside specialized namespaces. BigFix Agent DaemonSet Deployment - DaemonSet design model for executing BigFix security agents on underlying OpenShift worker nodes. Consolidation Roadmaps Infrastructure Consolidation Roadmap - Multi-phase migration plan for transitioning core homelab services and workloads from independent virtual machines to unified Kubernetes/OpenShift containers.Hugoen-usFri, 31 Jul 2026 00:00:00 +0000https://samplayskeys.github.io/Workspace/architecture/consolidation-roadmap/index.htmlFri, 31 Jul 2026 00:00:00 +0000https://samplayskeys.github.io/Workspace/architecture/consolidation-roadmap/index.htmlThis roadmap outlines the strategic phased approach for consolidating disparate, tag-drifted, or unmanaged GitOps clusters (environments) back into a fully version-controlled lifecycle managed off of a single main branch with tagging. Objective To eliminate repository drift, simplify environment configuration, and establish a clear promotion path by: Baselining all clusters onto a single trunk (main) with no active tags or branches. Cleaning up all unused/stale git branches and tags. Separating testing environments onto a dedicated long-lived Testing branch. Pinning all remaining environments (production, shared services) to a new, immutable release tag (v2.0). High-Level Flowchart flowchart TD %% Current State subgraph Current [Current State: Drift & Disparate Mapping] C_Prod[Prod Clusters / Tags/Branches] C_Test[Test Clusters / Diverse Tags] C_Unmanaged[Unmanaged Clusters / No Sync] end %% Phase 1 subgraph Phase1 [Phase 1: Trunk Consolidation] Main_Branch[(Git Repo: main branch)] P1_Sync[Point ALL Cluster GitOps/ResourceSync to main branch] P1_Clean[Prune all stale tags & inactive branches] end %% Phase 2 subgraph Phase2 [Phase 2: Testing Separation] Test_Branch[(Git Repo: Testing branch)] P2_Sync[Point Test Clusters to 'Testing' branch] end %% Phase 3 subgraph Phase3 [Phase 3: Version Stabilization] V2_Tag[(Git Tag: v2.0)] P3_Sync[Point Production & Other Clusters to 'v2.0' tag] end %% Transitions Current -->|Align and Point to main| P1_Sync P1_Sync -->|Prune old Git refs| P1_Clean P1_Clean -->|Create 'Testing' from main| Test_Branch Test_Branch -->|Configure Sync| P2_Sync P1_Clean -->|Tag main as v2.0| V2_Tag V2_Tag -->|Configure Sync| P3_Sync %% Styling style Current fill:#fdd,stroke:#f66,stroke-width:2px; style Phase1 fill:#ffd,stroke:#dd6,stroke-width:2px; style Phase2 fill:#dfd,stroke:#6b6,stroke-width:2px; style Phase3 fill:#ddf,stroke:#66b,stroke-width:2px; Phased Consolidation Plan Phase 1: Trunk Consolidation (Stabilization Baseline) Goal: Consolidate all GitOps controllers/ResourceSync configurations to point strictly to the main branch with zero tag/revision overrides.https://samplayskeys.github.io/Workspace/architecture/openshift/bigfix-agent-deployment/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://samplayskeys.github.io/Workspace/architecture/openshift/bigfix-agent-deployment/index.htmlOverview This guide details the architecture, design decisions, and configuration required to deploy the HCL BigFix Host Agent Client onto a Red Hat OpenShift Container Platform (OCP) cluster using Argo CD. This implementation rigorously adheres to and matches the standardized Helm component structures, sync-waves, and folder layouts defined in the helm-component-pattern artifact collection.https://samplayskeys.github.io/Workspace/architecture/openshift/bigfix-discovery-deployment/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://samplayskeys.github.io/Workspace/architecture/openshift/bigfix-discovery-deployment/index.htmlOverview This guide details the architecture, design decisions, and configuration required to deploy the HCL BigFix Inventory (BFI) discovery and sub-capacity licensing integration on Red Hat OpenShift Container Platform (OCP). This implementation rigorously adheres to and matches the standardized Helm component structures, sync-waves, and folder layouts defined in the helm-component-pattern artifact collection.https://samplayskeys.github.io/Workspace/architecture/openbao/tailscale-integration/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://samplayskeys.github.io/Workspace/architecture/openbao/tailscale-integration/index.htmlPlugin repository: https://github.com/SamPlaysKeys/openbao-plugin-secrets-tailscale This guide details how to set up an on-demand, dynamic Tailscale integration in OpenBao. When a client (such as a Docker container) requests a secret from docker/tailscale/auth-token/<name> (for example, docker/tailscale/auth-token/nginx), OpenBao will automatically call the Tailscale API to generate a short-lived, preauthorized, and ephemeral authentication key labeled for that specific container, returning it to the client immediately. Architectural Choices & Routing Can we support other paths later (e.g., docker/tailscale/idp)? Yes, absolutely. You have two clean options to achieve this: