Changing default chart settings (node SBOM,mTLS, Admission controller, and HTTP)

[slashben]

This pull request includes major changes to the kubescape-operator Helm charts to change default configuration options and enable additional security capability. The most important changes include enabling certain features by default, modifying conditions for enabling HTTP visiblity, and enabling mTLS for storage.

Configuration enhancements:

• charts/kubescape-operator/templates/node-agent/configmap.yaml: Modified the condition for enabling httpDetection also to consider runtimeDetection and runtimeObservability settings.

Default capability changes:

• charts/kubescape-operator/values.yaml: Enabled nodeSbomGeneration by default to ensure comprehensive vulnerability scanning.
• charts/kubescape-operator/values.yaml: Enabled admissionController by default for enhanced security.

Security improvements:

• charts/kubescape-operator/values.yaml: Enabled mTLS for storage to enhance security.

[gitguardian]

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15748363	Triggered	RSA Private Key	f56dbae	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
15748364	Triggered	RSA Private Key	f56dbae	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
15748336	Triggered	RSA Private Key	c48f541	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
15748365	Triggered	RSA Private Key	f56dbae	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
15748366	Triggered	RSA Private Key	f56dbae	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[matthyx]

we will definitely update the minor version for this one

[matthyx]

@slashben looks like the cert generation if failing the unit test - can we pin the randomness?