feat: Rollout 5.2.0 by akshatsinha007 · Pull Request #6889 · devtron-labs/devtron

akshatsinha007 · 2025-12-10T11:55:16Z

Description

Fixes #6894

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

This pull request introduces version 5.2.0 of the Helm chart, enhancing Istio configurations with new TCP settings and improving deployment templates with dynamic container naming.
It also includes SQL scripts for managing chart references, ensuring that outdated references are removed while new ones are added.
This pull request introduces several new features, including the management of external secrets through various secret managers, the ability to render raw YAML configurations, and the implementation of a Horizontal Pod Autoscaler that adapts to different Kubernetes versions, improving flexibility and scalability.
This pull request introduces several new Istio configurations as part of the rollout for version 5.1.1, including AuthorizationPolicy, DestinationRule, Gateway, and PeerAuthentication templates, enhancing the security and traffic management capabilities of the application.
This pull request introduces significant enhancements to the deployment configuration for version 5.1.1, adding support for environment variables sourced from various fields, secrets, and config maps, as well as liveness and readiness probes to ensure the application is running correctly.
Overall, these changes aim to improve security, traffic management, and deployment strategies, introducing new configurations and features in the Helm chart.

gitguardian · 2025-12-10T11:55:22Z

⚠️ GitGuardian has uncovered 3 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
9257608	Triggered	Base64 AWS keys	`968791e`	scripts/devtron-reference-helm-charts/deployment-chart_4-22-0/test-values.json	View secret
2763127	Triggered	Generic High Entropy Secret	`84e678f`	scripts/devtron-reference-helm-charts/reference-chart_5-1-1/secrets-test-values.yaml	View secret
141558	Triggered	Generic High Entropy Secret	`968791e`	scripts/devtron-reference-helm-charts/deployment-chart_4-22-0/env-values.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

Understand the implications of revoking this secret by investigating where it is used in your code.
Replace and store your secrets safely. Learn here the best practices.
Revoke and rotate these secrets.
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 · 2025-12-10T11:55:37Z