Know exactly where each fact comes from.
Fortem combines several data sources without pretending they are interchangeable. These notes make the security, availability, and measurement boundaries explicit.
Kubernetes product notes
01Local access and credential boundariesKubeconfig, exec-auth helpers, private endpoints, loopback binding, read-only defaults, and explicit management mode.02Requests, limits, and observed usageWhat comes from the Kubernetes API, what needs metrics-server, and why unavailable data never becomes a zero.03Traffic signals and their measurement pointWhich part of a request path Kubernetes can show, what an existing Prometheus counter measures, and what still needs application evidence.04Current scope and open integrationsWhat is implemented now, what remains optional, and what Fortem deliberately does not install in the cluster.
Previous ECS research
Preserved for engineers researching AWS ECS and Fargate. Product references inside these pages describe an earlier Fortem iteration, not the current Kubernetes tool.
Inspect the implementation, not a screenshot.
Install locally with your coding agent, use synthetic demo data first, then verify each optional source against a context you control.
or install yourself
Local install · read-only first · no Helm chart