kubescape / helm-charts

Kubescape can run as a set of microservices inside a Kubernetes cluster. This allows you to continually monitor the status of a cluster, including for compliance and vulnerability management
Apache License 2.0
29 stars 41 forks source link

Problems following the quick start guide #503

Open joaorocha-ceiia opened 3 weeks ago

joaorocha-ceiia commented 3 weeks ago

Description

Using the official quickstart guide, I followed the steps and the operator pod keeps restarting, outputting this to the logs

{"level":"fatal","ts":"2024-09-13T15:46:45Z","msg":"open /etc/config/matchingRules.json: no such file or directory","error":"open /etc/config/matchingRules.json: no such file or directory"}

Surely there's something that I'm missing, but the guide specifies that it should just work. For example, running the command

kubectl get vulnerabilitysummaries

doesnt output anything.

Environment

OS: Container-Optimized OS from Google Version: v1.29.7-gke.1104000

Steps To Reproduce

  1. helm repo add kubescape https://kubescape.github.io/helm-charts/ ; helm repo update ; helm upgrade --install kubescape kubescape/kubescape-operator -n kubescape --create-namespace --set clusterName=kubectl config current-context --set capabilities.continuousScan=enable

  2. Let every pod settle and check the status of the operator pod

Expected behavior

The operator pod should work without problems and scan the cluster

Actual Behavior

Operator pod keeps restarting

playworker commented 4 days ago

If you remove --set capabilities.continuousScan=enable then it should work, this setting seems to have been removed recently but the docs haven't been updated yet