C1: doc review — replicating-blumeops tutorial #350
2 changed files with 9 additions and 4 deletions
Merge branch 'main' into doc-review/replicating-blumeops
commit
89cf089edc
|
|
@ -196,11 +196,15 @@ controls:
|
||||||
description: >-
|
description: >-
|
||||||
Alloy collects pod logs and ships them to Loki, providing an
|
Alloy collects pod logs and ships them to Loki, providing an
|
||||||
audit trail for cluster activity. Compensates for missing
|
audit trail for cluster activity. Compensates for missing
|
||||||
apiserver audit logging which minikube does not configure.
|
apiserver audit logging which neither minikube (indri) nor
|
||||||
|
k3s (ringtail) configures by default.
|
||||||
created: 2026-03-30
|
created: 2026-03-30
|
||||||
last-reviewed: 2026-03-30
|
last-reviewed: 2026-05-11
|
||||||
notes: >-
|
notes: >-
|
||||||
Verify Alloy DaemonSet is running and Loki is receiving logs.
|
Verify Alloy DaemonSet is running on each cluster (alloy-k8s on
|
||||||
|
minikube, alloy-ringtail on k3s) and Loki is receiving logs.
|
||||||
Note this is weaker than native apiserver audit logs — it
|
Note this is weaker than native apiserver audit logs — it
|
||||||
captures pod stdout/stderr, not API request-level auditing.
|
captures pod stdout/stderr, not API request-level auditing.
|
||||||
Consider enabling minikube audit logging if supported.
|
Consider enabling apiserver audit logging on k3s post-migration
|
||||||
|
(`--audit-log-path` / `--audit-policy-file`) — minikube made it
|
||||||
|
hard, k3s makes it straightforward.
|
||||||
|
|
|
||||||
|
|
@ -0,0 +1 @@
|
||||||
|
Reviewed compensating control `observability-stack-audit`. Updated description to cover ringtail's k3s as well as indri's minikube; both Alloy DaemonSets and Loki are healthy.
|
||||||
Loading…
Add table
Add a link
Reference in a new issue