Skip to content
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.

Sign up for GitHub

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

Remove hostNetwork/hostPID #154

Merged
merged 1 commit into from
Mar 10, 2025
Merged

Remove hostNetwork/hostPID #154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions charts/docker-mailserver/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,16 +43,6 @@ deployment:
## Optionally specify a nodeSelector for the deployment
nodeSelector: {}

## Use the host’s network namespace. If this option is set, the ports that
## will be used must be specified.
## Ref: https://kubernetes.io/docs/api-reference/v1/definitions/#_v1_podspec
# pod.dockermailserver.hostNetwork will configure the pod to use the host's network namespace
hostNetwork: false
## Use the host’s pid namespace
## Ref: https://kubernetes.io/docs/api-reference/v1/definitions/#_v1_podspec
# pod.dockermailserver.hostPID defines whether the pod should use the host's PID namespace (default false)
hostPID: false

## Update strategy - only really applicable for deployments with RWO PVs attached
## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
## PV, and the "incoming" pod can never start. Setting the strategy to "Recreate" (our default) will
Expand Down
Loading