-
Notifications
You must be signed in to change notification settings - Fork 21
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
GD-9068: Security improvements #97
Merged
mihailradkov
merged 11 commits into
GDB-9425-version-11
from
GDB-9068-security-improvements
May 20, 2024
Merged
GD-9068: Security improvements #97
mihailradkov
merged 11 commits into
GDB-9425-version-11
from
GDB-9068-security-improvements
May 20, 2024
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
- Added `security.admin` for configuring the username and/or the password of the administrator user - Added `security.users` for inserting additional users into the default initial user.js configuration
Added default resource limits and requests for all init containers and provisioning jobs
- Enabled security context by default for all pods and containers - Added `initContainerDataPermissions` and `proxy.initContainerDataPermissions` for changing permissions in the storage volumes if needed - Updated the chart to require Kubernetes version 1.26+
- Added `extraVolumeClaimTemplates` and `proxy.extraVolumeClaimTemplates`
- Moved `persistence.volumeClaimTemplateSpec` to `persistence.volumeClaimTemplate.spec` - Added `persistence.emptyDir` and `proxy.persistence.emptyDir` configurations for an emptyDir volume that will be used when the persistence is disabled - Added configurations for extra `labels` and `annotations` for all persistent volume claim templates: `persistence.volumeClaimTemplate`, `proxy.persistence.volumeClaimTemplate` and `import.volumeMount.volumeClaimTemplate`
mihailradkov
commented
May 15, 2024
mihailradkov
commented
May 15, 2024
yaskoo
approved these changes
May 17, 2024
mihailradkov
force-pushed
the
GDB-9068-security-improvements
branch
from
May 20, 2024 05:33
621d9f0
to
7794feb
Compare
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.
GDB-9068: Update the admin user default details
security.admin
for configuring the username and/or the password of the administrator usersecurity.users
for inserting additional users into the default initial user.js configurationGDB-9440: Add resource limits for all containers
GDB-9437: Enabled the Security Context by default
initContainerDataPermissions
andproxy.initContainerDataPermissions
for changing permissions in the storage volumes if neededAdded configurations for extra PVC templates
extraVolumeClaimTemplates
andproxy.extraVolumeClaimTemplates
Added support for emptyDir persistence
persistence.volumeClaimTemplateSpec
topersistence.volumeClaimTemplate.spec
persistence.emptyDir
andproxy.persistence.emptyDir
configurations for an emptyDir volume that will be used when the persistence is disabledlabels
andannotations
for all persistent volume claim templates:persistence.volumeClaimTemplate
,proxy.persistence.volumeClaimTemplate
andimport.volumeMount.volumeClaimTemplate
Additionally