You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During a scan of a cluster, there may be custom resource definitions which own a pod beyond the stated list on the readme.md file - for example runners from summerwind.
Whilst an error about these owners is presented, the pod itself is not scanned. As such any pods mounting the docker host socket with an unknown owner will not be presented in the conclusion table.
I propose this tool scans the pod for the mount in the event the owner is unknown instead of ignoring it.
Replication:
Install an addon which controls pods, for example SummerWind Action Runners
Mount the Docker host socket with a runner
Run the tool
Output:
could not find resource manager for type Runner for pod my-docker-9k99f-12345
NAMESPACE TYPE NAME STATUS
The text was updated successfully, but these errors were encountered:
During a scan of a cluster, there may be custom resource definitions which own a pod beyond the stated list on the readme.md file - for example runners from summerwind.
Whilst an error about these owners is presented, the pod itself is not scanned. As such any pods mounting the docker host socket with an unknown owner will not be presented in the conclusion table.
I propose this tool scans the pod for the mount in the event the owner is unknown instead of ignoring it.
Replication:
Install an addon which controls pods, for example SummerWind Action Runners
Mount the Docker host socket with a runner
Run the tool
Output:
The text was updated successfully, but these errors were encountered: