-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Harmonize helm #11168
Harmonize helm #11168
Conversation
DryRun Security SummaryThe pull request focuses on improving the deployment and configuration of the DefectDojo application in a Kubernetes environment, with a focus on security-related aspects such as improved secret management, secure configuration settings, network segmentation, flexible configurations, and monitoring and observability. Expand for full summarySummary: The code changes in this pull request are focused on improving the deployment and configuration of the DefectDojo application in a Kubernetes environment. The changes span several Kubernetes resource templates, including ConfigMaps, Deployments, Services, Secrets, and Network Policies. The key security-related aspects of these changes include:
Overall, the code changes in this pull request appear to be focused on improving the security, configurability, and maintainability of the DefectDojo application deployment in a Kubernetes environment. While there are no major security concerns identified, it's important to thoroughly review the entire application and infrastructure setup to ensure that there are no other potential vulnerabilities or security risks. Files Changed:
Code AnalysisWe ran Riskiness🟢 Risk threshold not exceeded. |
971180b
to
4f84357
Compare
3f72c4f
to
ee993a7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for tidying these other blocks up. Just a few tweaks required here
ee993a7
to
4f468e6
Compare
Signed-off-by: Julien Godin <[email protected]>
4f468e6
to
859fee9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thanks for your work on this
Do i need to do anything else to see this merged ? |
We'll need to get some other reviewers to approve it, but I think it's good to go. Any other thoughts before we merge @dsever ? |
@cneill fine to me |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As an improvement, I do not see any issue here. I tested this change locally on a small setup as well.
- I would probably use "common helper" for the future
- but it might be done in the next PR - now there is no reason to block this PR; it is a "nice to have"-feature
- And I would add these labels to
gke-managed-certificate.yaml
as well- but this would need to be tested by people using this functionality. I do not have experience with it and I'm unable to test possible side effects (maybe there are not any but I can not be sure).
Description
Harmonize the different labels in the helm chart.
After @dsever and @cneill comments on the previous PR.
See #11108