Description:
When integrating ThreatMapper with Kubernetes KOPS clusters, I observed that hosts and nodes are detected, but pods/containers are not visible. As a result, ThreatMapper is unable to scan container images that are actively deployed in the cluster.
Steps to Reproduce:
- Deploy ThreatMapper in a KOPS‑managed Kubernetes cluster.
- Verify that nodes and hosts appear in the ThreatMapper dashboard.
- Attempt to view pods/containers or trigger image scans.
- Notice that pods are missing and image scans do not run.
Expected Behavior:
ThreatMapper should detect pods and containers in KOPS clusters and allow scanning of deployed images.
Actual Behavior:
Only hosts and nodes are visible. Pods are not detected, and deployed images cannot be scanned.
Environment Details:
- Kubernetes distribution: KOPS
- Cloud provider: AWS
- Container runtime: containerd
Impact:
This prevents vulnerability scanning of deployed workloads, limiting ThreatMapper’s effectiveness in compliance and runtime security monitoring.
Description:
When integrating ThreatMapper with Kubernetes KOPS clusters, I observed that hosts and nodes are detected, but pods/containers are not visible. As a result, ThreatMapper is unable to scan container images that are actively deployed in the cluster.
Steps to Reproduce:
Expected Behavior:
ThreatMapper should detect pods and containers in KOPS clusters and allow scanning of deployed images.
Actual Behavior:
Only hosts and nodes are visible. Pods are not detected, and deployed images cannot be scanned.
Environment Details:
Impact:
This prevents vulnerability scanning of deployed workloads, limiting ThreatMapper’s effectiveness in compliance and runtime security monitoring.