feat: enable FIPS 140 compliance in Dockerfile builds #1626
+4
−3
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Changes proposed in this pull request:
Pre-Merge Checklist
Consider all the following items. If your contribution violates any of them, or you are not sure about it, add a comment to the PR.
[ ] The code coverage is acceptable.[ ] Release notes for the introduced changes are created.[ ] If Kubebuilder changes were made, you ranmake generate-manifestsand committed the changes before the merge.[ ] Pre-existing managed resources are correctly handled.[ ] The change works on all hyperscalers supported by SAP BTP, Kyma runtime.[ ] There is no upgrade downtime.[ ] For infrastructure changes, you checked if the changes affect the hyperscaler's costs.[ ] RBAC settings are as restrictive as possible.[ ] If any new libraries are added, you verified license compliance and maintainability, and made a comment in the PR with details. We only allow stable releases to be included in the project.[ ] You checked if this change should be cherry-picked to active release branches.[ ] The configuration does not introduce any additional latency.Related issues