Skip to content
New issue

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

Problems following the quick start guide #503

Open
joaorocha-ceiia opened this issue Sep 13, 2024 · 0 comments
Open

Problems following the quick start guide #503

joaorocha-ceiia opened this issue Sep 13, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@joaorocha-ceiia
Copy link

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

@joaorocha-ceiia joaorocha-ceiia added the bug Something isn't working label Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant