20231107 release to main #289
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
git-flow start
S3support dev에서 테스트를 위해 임의 merge
s3support: change release name
release -> develop merge (230731)
finish release v3.0.0 ( develop merge from main )
update lma-addson chart version
최소사항 클러스터 지원을 위한 여정
add tks-admin-tools group
Fix byoh chart version
fix typo
bugfix. change release name to tks-apis
Clone ingress nginx
Minio의 버킷 생성 명 변경
1023 develop -> release ( v3.1.0 )
change default loki's bucket name from loki to tks-loki
make the upstream cluster-autoscaler chart common to all
remove unused cluster-autoscaler values
release to develop ( 231031)
minor modification for skb installation
update aws-ebs-csi chart to v2.24.0
kube-prometheus-operator: bumpup due to update function for status
Jaeger SSO 기능 추가
minor fix. change app name
20231103 release to develop
lma-addons: bumpup 기존 개발물에 영향도가 없으므로 merge
minio: change value key
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 8178259 | Generic Database Assignment | bde3d03 | tks-admin-tools/base/resources.yaml | View secret |
| 8178259 | Generic Database Assignment | 9d487ae | tks-admin-tools/base/resources.yaml | View secret |
| 8178259 | Generic Database Assignment | 79e23e2 | tks-admin-tools/base/resources.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.
Our GitHub checks need improvements? Share your feedbacks!
[WIP] 20231107 develop to release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.