Add OpenShift support with ServiceAccount and Security Context#14
Open
phoenix-bjoern wants to merge 1 commit into
Open
Add OpenShift support with ServiceAccount and Security Context#14phoenix-bjoern wants to merge 1 commit into
phoenix-bjoern wants to merge 1 commit into
Conversation
This commit addresses issue #10 by adding native OpenShift support to the Helm chart. Changes: - Add ServiceAccount template with configurable options - Configure pod and container security contexts for non-root execution (UID 999) - Add security hardening (drop capabilities, prevent privilege escalation) - Add comprehensive OpenShift deployment documentation in README.md - Update deployment template to reference ServiceAccount
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.
This PR adds native OpenShift support to the Helm chart, resolving issue #10.
Changes
OpenShift Compatibility
The chart now automatically creates a ServiceAccount and configures all security contexts to match the
owasp/modsecurity-crscontainer requirements (runs as httpd user, UID 999).Users only need to bind the ServiceAccount to a compatible SCC (e.g.,
nonroot-v2) after installation: