Adding the generation of keys and certificates for the storage service

[slashben]

Overview

This is part of solving kubescape/storage#117
and requires kubescape/storage#145 to be merged and released

In this PR we are setting up storage with:

1. CA Certificate
2. Signed server certificate and key
3. API server to require the above CA Certificate
4. Storage to require API server client certificate

[gitguardian]

⚠️ GitGuardian has uncovered 8 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
13676262	Triggered	RSA Private Key	87b51f9	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
13676262	Triggered	RSA Private Key	2575fd8	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
13676263	Triggered	RSA Private Key	87b51f9	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
13676263	Triggered	RSA Private Key	2575fd8	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
13676264	Triggered	RSA Private Key	87b51f9	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
13676264	Triggered	RSA Private Key	2575fd8	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
13676265	Triggered	RSA Private Key	87b51f9	charts/kubescape-operator/tests/snapshot/snapshot_test.yaml.snap	View secret
13676265	Triggered	RSA Private Key	2575fd8	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]

@slashben can you reopen this PR and confirm it works? I had issues with my kind cluster validating the previous release...