-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: add values to fix upstream flavor
- Loading branch information
1 parent
2abd7ed
commit e1d3f60
Showing
1 changed file
with
34 additions
and
0 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,37 @@ | ||
# image: | ||
# repository: confluence | ||
# tag: 9.9.3-{{ .Values.edition }} | ||
|
||
confluence: | ||
# -- Whether to apply security context to pod. | ||
# | ||
securityContextEnabled: true | ||
|
||
securityContext: | ||
|
||
# -- The GID used by the Confluence docker image | ||
# GID will default to 2002 if not supplied and securityContextEnabled is set to true. | ||
# This is intended to ensure that the shared-home volume is group-writeable by the GID used by the Confluence container. | ||
# However, this doesn't appear to work for NFS volumes due to a K8s bug: https://github.com/kubernetes/examples/issues/260 | ||
fsGroup: 2002 | ||
runAsUser: 2002 | ||
runAsGroup: 2002 | ||
runAsNonRoot: true | ||
|
||
# -- Standard K8s field that holds security configurations that will be applied to a container. | ||
# https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ | ||
# | ||
containerSecurityContext: | ||
runAsUser: 2002 | ||
runAsGroup: 2002 | ||
runAsNonRoot: true | ||
|
||
# -- Boolean to define whether to set local home directory permissions on startup | ||
# of Confluence container. Set to 'false' to disable this behaviour. | ||
# | ||
setPermissions: true | ||
|
||
volumes: | ||
sharedHome: | ||
nfsPermissionFixer: | ||
enabled: false |