Cronjob chart 1 7 0

[neha130]

Description

Fixes #

Checklist:

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR requires documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have tested it for all user roles.
• I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

Summary by Bito

• Deleted old release notes for versions v2.0.0 and v2.1.0 from CHANGELOG directory.
• Updated README.md to change branding from 'AI-Native Kubernetes Management Platform' to 'Kubernetes Dashboard for a Centralized DevOps Hub', removed scarf pixel, and updated links including adding Twitter and changing documentation URLs.
• Added new reference Helm charts for cronjob (1-7-0), deployment (4-22-0), reference (5-2-0), and statefulset (5-2-0) with associated templates, values, and schema files.
• Updated Go dependencies in go.mod and go.sum, regenerated wire_gen.go, and updated numerous vendor files.
• Added SQL migration scripts for new chart references, finops tables, cost module installation, and velero backup/restore features.

[gitguardian]

⚠️ GitGuardian has uncovered 2 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
141558	Triggered	Generic High Entropy Secret	9f64418	scripts/devtron-reference-helm-charts/cronjob-chart_1-7-0/env-values.yaml	View secret
2763127	Triggered	Generic High Entropy Secret	9f64418	scripts/devtron-reference-helm-charts/cronjob-chart_1-7-0/secrets-test-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 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.}

[github-actions]

Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n

[github-actions]

Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n

[sonarqubecloud]

Quality Gate failed

Failed conditions
E Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE