Troubleshooting Kubernetes® Security Posture Management (KSPM)

Existing Kyverno installation detected and has to be removed manuallyExisting Kyverno installation detected and has to be removed manually

A Kyverno admission controller was previously installed in the cluster. For the KSPM admission controller to work correctly, Kyverno must be removed during installation. When deleting Kyverno, you must also remove all CustomResourceDefinitions it created:

kubectl delete crd $(kubectl get crd -o name | grep kyverno.io)

Unable to check for existing Kyverno installationUnable to check for existing Kyverno installation

An unexpected error occurred while checking the cluster for the presence of Kyverno. Contact support.

Cluster version too oldCluster version too old

The specified cluster version is not supported. Upgrade the cluster to a supported version.

Insufficient permissions in the clusterInsufficient permissions in the cluster

The service account specified when activating the module does not have access to the cluster. Make sure the account has the security-deck.worker role.

Unable to check permissions in the clusterUnable to check permissions in the cluster

An unexpected error occurred while checking access permissions in the cluster. Either the cluster is unavailable or access is restricted by network policies.

Component is unhealthyComponent is unhealthy

Component operation error. Contact support.

Component sync failedComponent sync failed

An unexpected error occurred while modifying the component. Contact support.