feat(security): CIS Benchmark Level 1 + PSS restricted compliance (v0.2.5)#9
Merged
Merged
Conversation
Align server, agent and apiserver resource defaults with Absyss official prerequisites: - server: CPU 50m→250m req / RAM 128Mi→512Mi req / RAM 1Gi→2Gi limit - agent: CPU 20m→100m req / CPU 200m→500m limit / RAM 64Mi→256Mi req / RAM 256Mi→2Gi limit - apiserver: CPU 20m→500m req / CPU 500m→2000m limit / RAM 1Gi req / RAM 4Gi limit Bumps chart version to 0.2.4.
….2.5) - Add runAsGroup and fsGroup to securityContext values (configurable, null-safe for OpenShift) - Set runAsGroup: 1000 / fsGroup: 1000 in all cloud profiles (uid/gid confirmed from running image) - Add readOnlyRootFilesystem: true on db-proxy sidecar (socat / cloud-sql-proxy) - Document security compliance (PSS restricted, CIS L1) in README.md and README-fr.md
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
2 participants
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.
Summary
runAsGroupandfsGrouptosecurityContextvalues block -- configurable, null-safe for OpenShiftrunAsGroup: 1000/fsGroup: 1000in all cloud profiles (uid/gid confirmed from a running pod viakubectl exec id)readOnlyRootFilesystem: trueon the db-proxy sidecar (socat / Cloud SQL Auth Proxy)README.mdandREADME-fr.mdCompliance status
restrictedreadOnlyRootFilesystemon application containers (upstream image constraint -- Absyss images write to their rootfs at runtime)Test plan
helm lintpasses on all 4 cloud profiles (azure, gcp, aws, onpremise)helm upgradeon GKE (validated in dev environment)readOnlyRootFilesystem: truefsGroup: 1000(no permission errors in pod logs)