We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I see the issue: I am scanning a minikube, and I see this in the policy:
"scanningScope": { "matches": [ "cloud" ] }
@rcohencyberarmor , @YiscahLevySilas1 Do you know why we restrict this control to the "cloud"?
I am scanning a simple cluster (I did not define secomp on any of my components), and it seems that Kubescape does not scan any resources.
Version: v2.9.0
v2.9.0
Run Kubescape:
kubescape scan control c-0210
All of the resources in the cluster should fail
Kubescape did not scan any resources:
Kubescape did not scan any of the resources, make sure you are scanning valid kubernetes manifests (Deployments, Pods, etc.)
The text was updated successfully, but these errors were encountered:
This control shouldn't be restricted to cloud, it's compatible with any k8s cluster
Sorry, something went wrong.
fixed in #526
No branches or pull requests
Update
I see the issue:
I am scanning a minikube, and I see this in the policy:
@rcohencyberarmor , @YiscahLevySilas1 Do you know why we restrict this control to the "cloud"?
Description
I am scanning a simple cluster (I did not define secomp on any of my components), and it seems that Kubescape does not scan any resources.
Environment
Version:
v2.9.0
Steps To Reproduce
Run Kubescape:
Expected behavior
All of the resources in the cluster should fail
Actual Behavior
Kubescape did not scan any resources:
The text was updated successfully, but these errors were encountered: