Limitations

Cluster scanning

Cloud vendor integrations

Kubescape reads cluster information from the cloud vendors' API. Each vendor has a list of authorizations they require (see the SDK of the given vendor). Kubescape uses SDKs to retrieve this information. This authentication information must be available in the running environment of Kubescape

Vulnerability scanning

Private registries support

Scanning Troubleshooting

Issue / logsIssue DescriptionSolution
Unable to update vulnerability database: unable to download db
Failed to get image descriptor from registry
The image may be deleted from the container registry, so the vulnerability scanner can't get the image manifest data and it's vulnerabilities*## first solution suggestion:* The image needs to be added to the container registry to scan it
*## second solution suggestion:* Update your image in the pod to the latest image that exists in the container registry
* failed to load vulnerability db: vulnerability database is corruptWe reached the limit of the the process memory limited by the kubernetes deployment: "armo-vuln-scan"*## first solution suggestion:* Increase the memory limit of the deployment.
https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
*## second solution suggestion:* Reduce the number in the CA_MAX_VULN_SCAN_ROUTINS environment variable(the default is 4).