sync #2165

Closed

mfreeman451 wants to merge 17 commits from refs/pull/2165/head into updates/k8s_fixes

mfreeman451 commented

2025-08-27 02:27:02 +00:00

(Migrated from github.com)

Owner

Imported from GitHub pull request.

Original GitHub pull request: #1577
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/1577
Original created: 2025-08-27T02:27:02Z
Original updated: 2025-08-27T02:28:28Z
Original head: carverauto/serviceradar:main
Original base: updates/k8s_fixes

No description provided.

Imported from GitHub pull request. Original GitHub pull request: #1577 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/pull/1577 Original created: 2025-08-27T02:27:02Z Original updated: 2025-08-27T02:28:28Z Original head: carverauto/serviceradar:main Original base: updates/k8s_fixes --- _No description provided._

gitguardian[bot] commented

2025-08-27 02:27:40 +00:00

(Migrated from github.com)

Author

Owner

Imported GitHub PR comment.

Original author: @gitguardian[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/1577#issuecomment-3226531384
Original created: 2025-08-27T02:27:40Z

⚠️ 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
20438075	Triggered	Kubernetes Docker Secret	`1ac03b2495`	k8s/demo/base/secrets.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 secret safely. Learn here the best practices.
Revoke and rotate this secret.
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.}

Imported GitHub PR comment. Original author: @gitguardian[bot] Original URL: https://github.com/carverauto/serviceradar/pull/1577#issuecomment-3226531384 Original created: 2025-08-27T02:27:40Z --- #### ⚠️ 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. <details> <summary>🔎 Detected hardcoded secret in your pull request</summary> | GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [20438075](https://dashboard.gitguardian.com/workspace/312055/incidents/20438075?occurrence=209999406) | Triggered | Kubernetes Docker Secret | 1ac03b2495314b6efeb941a84a6e9fd8c32a4874 | k8s/demo/base/secrets.yaml | [View secret](https://github.com/carverauto/serviceradar/commit/1ac03b2495314b6efeb941a84a6e9fd8c32a4874#diff-606d5c27a32fb978e98f7041e6dc6d30c013cec8052b8f48cf2f890c882b2022R26) | </details> <details> <summary>🛠 Guidelines to remediate hardcoded secrets</summary> 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/kubernetes_docker_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation. </details> --- 🦉 [GitGuardian](https://dashboard.gitguardian.com/auth/login/?utm_medium=checkruns&utm_source=github&utm_campaign=cr1) 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.