A government-compliant, open-source Kubernetes platform providing a hardened runtime for deploying containerized applications. Built on RKE2 (DISA STIG-certified), Rocky Linux 9.7 (FIPS 140-2 enabled), and the CNCF ecosystem. Targets ATO, CMMC 2.0 Level 2, FedRAMP Moderate, NIST 800-53 Rev 5, and DISA STIGs. Provides zero-trust networking (Istio mTLS STRICT), policy-as-code (Kyverno), full observability (Prometheus/Grafana/Loki/Tempo), secrets management (OpenBao + ESO), supply chain security (Harbor + Trivy + Cosign), and GitOps-driven deployment (Flux CD).
Authorization Boundary
The SRE authorization boundary encompasses the entire Kubernetes cluster including all control plane and worker nodes, the RKE2 distribution, all platform services deployed via Flux CD, the Istio service mesh, and all tenant workloads running within the cluster. External dependencies (DNS, NTP, upstream OS package repos) are outside the boundary. The cluster runs on Proxmox VE hypervisor infrastructure which is documented separately.
▼ 2. Information System Owner & Key Personnel
▼ 3. System Environment
3.1 Hardware Inventory
Hostname
Role
IP Address
OS
CPU
RAM
Storage
sre-cp-1
Control Plane (server)
192.168.2.10
Rocky Linux 9.7
4 vCPU
16 GB
100 GB
sre-worker-1
Worker (agent)
192.168.2.11
Rocky Linux 9.7
4 vCPU
16 GB
100 GB
sre-worker-2
Worker (agent)
192.168.2.12
Rocky Linux 9.7
4 vCPU
16 GB
100 GB
3.2 Software Inventory
Component
Version
Purpose
Layer
Rocky Linux
9.7
Base operating system (DISA STIG hardened, FIPS enabled, SELinux enforcing)
OS
RKE2
v1.34.4
DISA STIG-certified Kubernetes distribution (FIPS 140-2, CIS Benchmark)
Cluster
Flux CD
v2.8.1
GitOps engine — continuous reconciliation of cluster state from Git
Platform
Istio
1.25.2
Service mesh — mTLS STRICT, AuthorizationPolicy, traffic management
Core
Kyverno
3.3.7
Policy engine — admission control, image verification, Pod Security Standards
Core
cert-manager
1.14.4
Certificate lifecycle management — internal CA, Let's Encrypt integration
Identity & SSO — OIDC/SAML, MFA, RBAC group mapping
Addon
▼ 4. Authorization Boundary
The following diagram depicts the SRE authorization boundary, encompassing all cluster nodes, platform services, and tenant workloads. External systems (DNS, NTP, upstream repos, Proxmox hypervisor) are outside the boundary.