The Toolforge k8s-status tool can expose via anon web interface some information that may be considered sensitive.
The observer role for k8s-status allows it to read pods/status, which may contain an exit message produced by the user, see reference https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#containerstateterminated-v1-core
Examples of user-triggered workloads that may allow this info leak:
- build service pipelines
- all other cluster pods
Reduce k8s-status permissions to it cannot expose this information.