Added Clickhouse Charts

[samyakjain1908]

No description provided.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
31565202	Triggered	Generic Password	e4c2e06	charts/clickhouse/values.yaml	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.}

[sibasish-satapathy-ops]

The limits is set to very high spec as the kubernetes resources majorly plays around limits hence the chart basically requires a higher chunk of resources

[sibasish-satapathy-ops]

1. Need to Update the limits of the charts as the limits are on very high side.
2. need to control the namespace handling from the values. yaml
3. We can also control the storage class name from values. yaml file
4. Can we use prehooks to create secrets for the registry authentication.