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

CIS cannot be deployed into namespace other than cis-operator-system #236

Open
ravirajshankarl opened this issue Dec 8, 2023 · 0 comments

Comments

@ravirajshankarl
Copy link

ravirajshankarl commented Dec 8, 2023

ClusterScanNS = "cis-operator-system"

It looks like the namespace is hardcoded to cis-operator-system. I'm getting an error on creating a new on demand clusterscan

time="2023-12-06T14:31:17Z" level=error msg="error syncing 'cis-1.7-hardened': handler cis-operator: failed to create cis-
operator-system/security-scan-runner-cis-1.7-hardened batch/v1, Kind=Job for cis-operator cis-1.7-hardened: namespaces
 \"cis-operator-system\" not found, failed to create cis-operator-system/cis-s-config-cm-cis-1.7-hardened /v1, 
Kind=ConfigMap for cis-operator cis-1.7-hardened: namespaces \"cis-operator-system\" not found, failed to create cis-
operator-system/cis-s-plugins-cm-cis-1.7-hardened /v1, Kind=ConfigMap for cis-operator cis-1.7-hardened: namespaces 
\"cis-operator-system\" not found, failed to create cis-operator-system/service-rancher-cis-benchmark /v1, Kind=Service for 
cis-operator cis-1.7-hardened: namespaces \"cis-operator-system\" not found, requeuing"

Is it possible to configure the namespace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant