Files

6526 lines
294 KiB
YAML

# Copyright 2024-2025 New Vector Ltd
# Copyright 2025-2026 Element Creations Ltd
#
# SPDX-License-Identifier: AGPL-3.0-only
# This file is generated. Do not edit directly. Edit source/values.yaml.j2 instead to make changes
## Common configuration that impacts all components in the chart
## The matrix-tools image, used in multiple components
matrixTools:
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: ghcr.io
## The path in the registry where the container image is located
repository: element-hq/ess-helm/matrix-tools
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "0.10.9"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Configures sizeLimit (maximum size) and medium for this component's emptyDir volumes.
## Each sizeLimit is a Kubernetes quantity string, e.g. 10Mi.
## medium is either "Memory" (tmpfs-backed) or "" (node default storage).
ephemeralStorages:
## rendered-config emptyDir used in all components to render configuration
renderedConfig:
sizeLimit: 1Mi
medium: Memory
## Common resources across various matrix-tools commands
resources:
## Kubernetes resources to allocate to each instance.
renderConfig:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 10m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 50Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Kubernetes resources to allocate to each instance.
tcpWait:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 10m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 50Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## CertManager Issuer to configure by default automatically on all ingresses
## If configured, the chart will automatically generate the tlsSecret name for all ingresses
certManager: {}
## Choose one of clusterIssuer or issuer
# clusterIssuer:
# issuer:
## The server name of the Matrix Stack. This gets embedded in user IDs & room IDs
## It can not change after the initial deployment.
# serverName: ess.localhost
## Labels to add to all manifest for all components in this chart
labels: {}
## How all ingresses should be constructed by default, unless overridden
ingress:
## Annotations to be added to all Ingresses. Will be merged with component specific Ingress annotations
annotations: {}
## What Ingress Class Name that should be used for all Ingresses by default
# className:
## Disable TLS configuration by setting it to false
tlsEnabled: true
## The name of the Secret containing the TLS certificate and the key that should be used for all Ingresses by default
# tlsSecret:
## Optional Service override for all Ingresses.
## When a field is set, it overrides `httpService`. `<component>.httpService` takes precedence over this.
# service:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
service: {}
## If set, some tweaks will be applied automatically to ingresses based on the controller type here.
## This can be set to `ingress-nginx`.
# controllerType:
## Default configuration of the Service handling inbound HTTP(S) traffic.
## `<component>.httpService` takes precedence, then `<component>.ingress.service`, then `ingress.service`.
httpService:
type: ClusterIP
## Annotations to be added to all component Services. Will be merged with more specific Service annotations
annotations: {}
# External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
externalTrafficPolicy: Cluster
internalTrafficPolicy: Cluster
# External IPs addresses of this service.
# externalIPs: []
## Common image properties that are applied as defaults to all components.
image:
## The pullPolicy to use for all images. This overrides the pullPolicy used by the templates
## that varies based on whether the image is referenced by tag (uses `Always`) or by digest (uses `IfNotPresent`).
## Can be overriden by a specific `pullPolicy` on each image.
# pullPolicy: IfNotPresent
## A list of Secrets in this namespace to use as pull Secrets.
## If a given component specifies its own pull Secrets the 2 lists are merged.
## e.g.
## pullSecrets:
## - name: ess-pull-secret
pullSecrets: []
## Configures the defaults for all constructed PersistentVolumeClaims
storage:
## The StorageClass to be used by all constructed PersistentVolumeClaims by default.
## The top-level storage.storageClassName value is used, if not provided (or the cluster default if neither are provided).
## If changed after initial usage the PersistentVolumeClaim could be recreated causing data-loss.
# storageClassName:
## Whether to instruct Helm to keep or delete all constructed PersistentVolumeClaims by default when uninstalling the chart
resourcePolicy: keep
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## The global nodeSelector is used if a component does not provide its own nodeSelector.
nodeSelector: {}
## Workload tolerations allows Pods that are part of a (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for a component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for each component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for each component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints:
- maxSkew: 1
topologyKey: kubernetes.io/hostname
whenUnsatisfiable: ScheduleAnyway
## Default priorityClassName applied to the pods of all components.
## A priorityClassName set on an individual component overrides this global value for that component.
## Synapse worker pods inherit the priorityClassName of the Synapse main process; per-worker priorityClassName is not yet configurable.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## Default schedulerName applied to the pods of all components.
## A schedulerName set on an individual component overrides this global value for that component.
## Synapse worker pods inherit the schedulerName of the Synapse main process; per-worker schedulerName is not yet configurable.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## Default runtimeClassName applied to the pods of all components.
## A runtimeClassName set on an individual component overrides this global value for that component.
## Synapse worker pods inherit the runtimeClassName of the Synapse main process; per-worker runtimeClassName is not yet configurable.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## Default affinity rules applied to the pods of all components.
## Configured independently per affinity type (nodeAffinity, podAffinity, podAntiAffinity).
## A component that sets one of these affinity types overrides only that type for that component; the other types are still inherited from here.
## Synapse worker pods inherit the affinity of the Synapse main process; per-worker affinity is not yet configurable.
## Supports the three Kubernetes affinity types, each configured as a sub-key.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity:
## Node-scheduling rules for the pods. e.g.
## nodeAffinity:
## requiredDuringSchedulingIgnoredDuringExecution:
## nodeSelectorTerms:
## - matchExpressions:
## - key: disktype
## operator: In
## values:
## - ssd
nodeAffinity: {}
## Rules that attract the pods to nodes already running matching pods. e.g.
## podAffinity:
## preferredDuringSchedulingIgnoredDuringExecution:
## - weight: 100
## podAffinityTerm:
## topologyKey: kubernetes.io/hostname
## labelSelector:
## matchLabels:
## app.kubernetes.io/name: matrix-stack
podAffinity: {}
## Rules that repel the pods from nodes already running matching pods. e.g.
## podAntiAffinity:
## preferredDuringSchedulingIgnoredDuringExecution:
## - weight: 100
## podAffinityTerm:
## topologyKey: kubernetes.io/hostname
## labelSelector:
## matchLabels:
## app.kubernetes.io/name: matrix-stack
podAntiAffinity: {}
## The cluster's domain name which will be appended to URLs of internal Services (<name>.<namespace>.svc.<clusterDomain>).
## It is unusual to need to change this but if you do need to change it,
## strongly consider having a trailing dot to prevent multiple search domains being queried.
clusterDomain: "cluster.local."
## Networking configuration options that globally apply
networking:
## Whether components should attempt to bind IPv4 (ipv4) /IPv6 (ipv6) / both (dual-stack)
ipFamily: dual-stack
## Set the default inbound traffic handler type. Options are ingress | none
inboundTrafficHandler: ingress
## A dictionary of extra objects to be rendered into the cluster
## Each dictionary item can either be a single object as a string, e.g.
## extraObjects:
## fromString: |
## kind: ConfigMap
## ..
##
## or it can be a list of strings, e.g.
## extraObjects:
## inList:
## - |
## kind: ConfigMap
## ...
## - |
## kind: Secret
## ...
##
## All strings are templated and so can use `$.Release`, `$.Values`, etc.
extraObjects: {}
## Components
initSecrets:
enabled: true
rbac:
create: true
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in Init Secrets, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Init Secrets, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Init Secrets, as a yaml array
extraInitContainers: []
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10010
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10010
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10010
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 50m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 200Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
deploymentMarkers:
enabled: true
rbac:
create: true
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in Deployment Markers, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Deployment Markers, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Deployment Markers, as a yaml array
extraInitContainers: []
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10010
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10010
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10010
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 50m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 200Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
matrixRTC:
enabled: true
# Allows restricting room creation to local users only
# Remote federated users can still join the room
# Deprecated, will be removed when legacy MatrixRTC authoriser endpoints are removed
restrictRoomCreationToLocalUsers: true
# LiveKit Authentication Configuration
# This section allows you to configure authentication for the LiveKit SFU.
livekitAuth:
key: "matrix-rtc"
## The secret for the LiveKit SFU.
## If sfu.enabled=true, it will be generated by the `initSecrets` job if it is empty.
## It is required if sfu.enabled=false.
## It can either be provided inline in the Helm chart e.g.:
## secret:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## secret:
## secret: existing-secret
## secretKey: key-in-secret
# secret: {}
## The application service registration of the MatrixRTC Authorisation Service.
## The service uses it to act on behalf of users towards the homeserver, e.g. to manage their MSC4140 delayed leave events.
## It will be generated by the `initSecrets` job if it is empty.
## If synapse.enabled=true, Synapse loads it. Otherwise your homeserver must load the same registration,
## e.g. copied from the generated Secret. If your homeserver doesn't run in the same cluster,
## change its `io.element.msc4512.proxy_url` or remove both `io.element.msc4512.*` keys.
## It can either be provided inline in the Helm chart e.g.:
## appserviceRegistration:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## appserviceRegistration:
## secret: existing-secret
## secretKey: key-in-secret
# appserviceRegistration: {}
# The application service user of the MatrixRTC Authorisation Service, i.e. the `sender_localpart` of its registration.
# The service doesn't act as this user, only on behalf of the users of the homeserver.
# Ignored if appserviceRegistration is provided.
user:
localpart: _lk_jwt_service
## Details of the external Redis/Valkey to use
## Does not need to be set if the internal Valkey should be used
## This is useful for production environments where you want to use
## managed Redis/Valkey services (AWS Elasticache, Azure Cache for Redis, etc.)
# redisOrValkey:
## Redis/Valkey host
# host:
## Redis/Valkey port
# port: 6379
## Redis/Valkey database number (0-15)
# db: 0
## Redis/Valkey password (optional - many managed services require auth).
## It can either be provided inline in the Helm chart e.g.:
## password:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## password:
## secret: existing-secret
## secretKey: key-in-secret
# password: {}
## Enable TLS for Redis/Valkey connection
# tls: false
# Use 0 replicas to stop the MatrixRTC authoriser
replicas: 1
## Configuration of the Service handling inbound HTTP(S) traffic for this component.
## Takes precedence over `ingress.service` and the global `httpService`. Leave empty to inherit `httpService`.
# httpService:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
httpService: {}
## How this ingress should be constructed
ingress:
## What hostname should be used for this Ingress
# host:
## Annotations to be added to this Ingress
annotations: {}
## What Ingress Class Name that should be used for this Ingress
# className:
## Disable TLS configuration by setting it to false
tlsEnabled: true
## The name of the Secret containing the TLS certificate and the key that should be used for this Ingress
# tlsSecret:
## Optional Service override for this Ingress.
## When a field is set, it overrides `httpService`. `<component>.httpService` takes precedence over this.
# service:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
service: {}
## If set, some tweaks will be applied automatically to ingresses based on the controller type here.
## This can be set to `ingress-nginx`.
# controllerType:
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: oci.element.io
## The path in the registry where the container image is located
repository: lk-jwt-service
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "0.10.0"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Set DNS policy for the pod. Kubernetes defaults to ClusterFirst if no value is provided here
dnsPolicy: ""
## Pod-level DNS configuration. Only effective when dnsPolicy is set to "None".
dnsConfig: {}
## The list of hosts aliases to configure on the pod spec.
## It should be avoid as much as possible to use this feature.
## Please prefer using an DNS entry to resolve your hostnames.
## This can be used as a workaround when entries cannot be resolved using DNS, for example for our automated testings.
## e.g.
## hostAliases:
## - ip: 192.0.2.1 # An IP resolution to add to /etc/hosts
## # A list of hostnames to be associated with the above IP
## hostnames:
## - ess.localhost
## - synapse.ess.localhost
hostAliases: []
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in Matrix RTC, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Matrix RTC, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Matrix RTC, as a yaml array
extraInitContainers: []
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10033
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10033
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10033
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 50m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 200Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Whether to deploy ServiceMonitors into the cluster for this component
## Requires the ServiceMonitor CRDs to be in the cluster
serviceMonitors:
enabled: true
## List of RelabelConfig's to apply to the target before scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
relabelings: []
## List of RelabelConfig's to apply to the samples before ingestion but after scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
metricRelabelings: []
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
sfu:
enabled: true
## URL for an external SFU, using the wss schema
## Required if the in-chart SFU is disabled
# url: "wss://external.sfu.example.com"
# Use STUN to resolve the server public IP
useStunToDiscoverPublicIP: true
# Specify a manual IP address for the server public IP
manualIP: ""
# The Kubernetes downward API field used to populate the server public IP
# when useStunToDiscoverPublicIP is false and manualIP is empty
# Valid values: hostIP, podIP
nodeIPSource: hostIP
# LiveKit Logging level
logging:
# log level, valid values: debug, info, warn, error
level: info
# log level for pion, default error
pionLevel: error
# when set to true, emit json fields
json: false
## Additional configuration to provide to all LiveKit processes.
## This should be provided as yaml-string and will be merged into the default configuration.
## Each key under additional is an additional config to merge into LiveKit sfu-config.yaml
## Full details on available configuration options can be found at https://docs.livekit.io/home/self-hosting/deployment/#configuration
## This can be provided in-line in the Helm Chart and/or via an existing Secret
## e.g.
## additional:
## 0-customConfig:
## config: |
## <any valid configuration>
## 1-customConfig:
## configSecret: custom-config
## configSecretKey: shared.yaml
##
## Most settings are configurable but some settings are owned by the chart and can't overwritten
additional: {}
## Details of the external Redis/Valkey to use
## Does not need to be set if the internal Valkey should be used
## This is useful for production environments where you want to use
## managed Redis/Valkey services (AWS Elasticache, Azure Cache for Redis, etc.)
# redisOrValkey:
## Redis/Valkey host
# host:
## Redis/Valkey port
# port: 6379
## Redis/Valkey database number (0-15)
# db: 0
## Redis/Valkey password (optional - many managed services require auth).
## It can either be provided inline in the Helm chart e.g.:
## password:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## password:
## secret: existing-secret
## secretKey: key-in-secret
# password: {}
## Enable TLS for Redis/Valkey connection
# tls: false
# Use 0 replicas to stop the SFU
replicas: 1
# Whether to start the SFU in host network mode or not
hostNetwork: false
exposedServices:
rtcTcp:
enabled: true
# Annotations to be added to this service
# This is unused if the portType is `HostPort` as the pod port
# is exposed directly on the node running it, so no service is created.
annotations: {}
# Either a ClusterIP, NodePort, HostPort or LoadBalancer
# If the port is a HostPort, no Service will be created.
portType: NodePort
# External IPs addresses of this service.
# externalIPs: []
# Node Port template value. If empty, `nodePort` wont be set on the service port
# And kubernetes will automatically assign a port.
nodePort: "{{ .context.port }}"
# Either Local or Cluster
internalTrafficPolicy: Cluster
externalTrafficPolicy: Cluster
# The ipFamilyPolicy of the Service. Either SingleStack, PreferDualStack or RequireDualStack.
# If unset, the Service uses PreferDualStack when networking.ipFamily is dual-stack, SingleStack otherwise.
# ipFamilyPolicy: PreferDualStack
# The ipFamilies of the Service. A list containing IPv4 and/or IPv6.
# If unset, Kubernetes picks the families based on the ipFamilyPolicy.
# ipFamilies: []
port: 30001
rtcMuxedUdp:
enabled: true
# Annotations to be added to this service
# This is unused if the portType is `HostPort` as the pod port
# is exposed directly on the node running it, so no service is created.
annotations: {}
# Either a ClusterIP, NodePort, HostPort or LoadBalancer
# If the port is a HostPort, no Service will be created.
portType: NodePort
# External IPs addresses of this service.
# externalIPs: []
# Node Port template value. If empty, `nodePort` wont be set on the service port
# And kubernetes will automatically assign a port.
nodePort: "{{ .context.port }}"
# Either Local or Cluster
internalTrafficPolicy: Cluster
externalTrafficPolicy: Cluster
# The ipFamilyPolicy of the Service. Either SingleStack, PreferDualStack or RequireDualStack.
# If unset, the Service uses PreferDualStack when networking.ipFamily is dual-stack, SingleStack otherwise.
# ipFamilyPolicy: PreferDualStack
# The ipFamilies of the Service. A list containing IPv4 and/or IPv6.
# If unset, Kubernetes picks the families based on the ipFamilyPolicy.
# ipFamilies: []
port: 30002
rtcUdp:
enabled: false
# Annotations to be added to this service
# This is unused if the portType is `HostPort` as the pod port
# is exposed directly on the node running it, so no service is created.
annotations: {}
# Either a ClusterIP, NodePort, HostPort or LoadBalancer
# If the port is a HostPort, no Service will be created.
portType: NodePort
# External IPs addresses of this service.
# externalIPs: []
# Either Local or Cluster
internalTrafficPolicy: Cluster
externalTrafficPolicy: Cluster
# The ipFamilyPolicy of the Service. Either SingleStack, PreferDualStack or RequireDualStack.
# If unset, the Service uses PreferDualStack when networking.ipFamily is dual-stack, SingleStack otherwise.
# ipFamilyPolicy: PreferDualStack
# The ipFamilies of the Service. A list containing IPv4 and/or IPv6.
# If unset, Kubernetes picks the families based on the ipFamilyPolicy.
# ipFamilies: []
portRange:
# The beginning port of the range
startPort: 31000
# The last port of the range
endPort: 32000
# Node Port template value.
# The template takes as argument :
# - "context" : This exposed service values context, in addition with a key "port"
# containing current port number of the helm range
# - "root" : The $ helm root special context
# If empty, `nodePort` wont be set on the service port
# And kubernetes will automatically assign a port.
nodePort: "{{ .context.port }}"
turnTLS:
enabled: false
# Annotations to be added to this service
# This is unused if the portType is `HostPort` as the pod port
# is exposed directly on the node running it, so no service is created.
annotations: {}
# Either a ClusterIP, NodePort, HostPort or LoadBalancer
# If the port is a HostPort, no Service will be created.
portType: NodePort
# External IPs addresses of this service.
# externalIPs: []
# Node Port template value. If empty, `nodePort` wont be set on the service port
# And kubernetes will automatically assign a port.
nodePort: "{{ .context.port }}"
# Either Local or Cluster
internalTrafficPolicy: Cluster
externalTrafficPolicy: Cluster
# The ipFamilyPolicy of the Service. Either SingleStack, PreferDualStack or RequireDualStack.
# If unset, the Service uses PreferDualStack when networking.ipFamily is dual-stack, SingleStack otherwise.
# ipFamilyPolicy: PreferDualStack
# The ipFamilies of the Service. A list containing IPv4 and/or IPv6.
# If unset, Kubernetes picks the families based on the ipFamilyPolicy.
# ipFamilies: []
port: 30003
# The domain of the service
domain: ""
# The TLS secret used to expose this service
# Optional when tlsTerminationOnPod is false (external termination) or when certManager is configured
tlsSecret: ""
# Whether TLS termination should happen on the pod (true) or externally (false)
# When false, TLS termination is handled by an external load balancer or proxy
tlsTerminationOnPod: true
turn:
enabled: false
# Annotations to be added to this service
# This is unused if the portType is `HostPort` as the pod port
# is exposed directly on the node running it, so no service is created.
annotations: {}
# Either a ClusterIP, NodePort, HostPort or LoadBalancer
# If the port is a HostPort, no Service will be created.
portType: NodePort
# External IPs addresses of this service.
# externalIPs: []
# Node Port template value. If empty, `nodePort` wont be set on the service port
# And kubernetes will automatically assign a port.
nodePort: "{{ .context.port }}"
# Either Local or Cluster
internalTrafficPolicy: Cluster
externalTrafficPolicy: Cluster
# The ipFamilyPolicy of the Service. Either SingleStack, PreferDualStack or RequireDualStack.
# If unset, the Service uses PreferDualStack when networking.ipFamily is dual-stack, SingleStack otherwise.
# ipFamilyPolicy: PreferDualStack
# The ipFamilies of the Service. A list containing IPv4 and/or IPv6.
# If unset, Kubernetes picks the families based on the ipFamilyPolicy.
# ipFamilies: []
port: 30004
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: docker.io
## The path in the registry where the container image is located
repository: livekit/livekit-server
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "v1.13.11"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in Matrix RTC SFU, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Matrix RTC SFU, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Matrix RTC SFU, as a yaml array
extraInitContainers: []
## The list of hosts aliases to configure on the pod spec.
## It should be avoid as much as possible to use this feature.
## Please prefer using an DNS entry to resolve your hostnames.
## This can be used as a workaround when entries cannot be resolved using DNS, for example for our automated testings.
## e.g.
## hostAliases:
## - ip: 192.0.2.1 # An IP resolution to add to /etc/hosts
## # A list of hostnames to be associated with the above IP
## hostnames:
## - ess.localhost
## - synapse.ess.localhost
hostAliases: []
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Set DNS policy for the pod. Kubernetes defaults to ClusterFirst if no value is provided here
dnsPolicy: "{{ $.Values.matrixRTC.sfu.hostNetwork | ternary \"ClusterFirstWithHostNet\" \"\" }}"
## Pod-level DNS configuration. Only effective when dnsPolicy is set to "None".
dnsConfig: {}
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10030
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10030
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10030
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 150Mi
cpu: 100m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 4Gi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Whether to deploy ServiceMonitors into the cluster for this component
## Requires the ServiceMonitor CRDs to be in the cluster
serviceMonitors:
enabled: true
## List of RelabelConfig's to apply to the target before scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
relabelings: []
## List of RelabelConfig's to apply to the samples before ingestion but after scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
metricRelabelings: []
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
elementAdmin:
enabled: true
# Number of Element Admin replicas to start up
replicas: 1
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: oci.element.io
## The path in the registry where the container image is located
repository: element-admin
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "0.1.19"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Configuration of the Service handling inbound HTTP(S) traffic for this component.
## Takes precedence over `ingress.service` and the global `httpService`. Leave empty to inherit `httpService`.
# httpService:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
httpService: {}
## How this ingress should be constructed
ingress:
## What hostname should be used for this Ingress
# host:
## Annotations to be added to this Ingress
annotations: {}
## What Ingress Class Name that should be used for this Ingress
# className:
## Disable TLS configuration by setting it to false
tlsEnabled: true
## The name of the Secret containing the TLS certificate and the key that should be used for this Ingress
# tlsSecret:
## Optional Service override for this Ingress.
## When a field is set, it overrides `httpService`. `<component>.httpService` takes precedence over this.
# service:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
service: {}
## If set, some tweaks will be applied automatically to ingresses based on the controller type here.
## This can be set to `ingress-nginx`.
# controllerType:
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in Element Admin, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Element Admin, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Element Admin, as a yaml array
extraInitContainers: []
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10104
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10104
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10104
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 50m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 200Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## How long, in seconds, each container of this workload waits before stopping when it rolls out
## This gives the Service time to update its iptables rules before the pod is killed
## Unset this to stop the containers without waiting
preStopSleepSeconds: 3
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configures sizeLimit (maximum size) and medium for this component's emptyDir volumes.
## Each sizeLimit is a Kubernetes quantity string, e.g. 10Mi.
## medium is either "Memory" (tmpfs-backed) or "" (node default storage).
ephemeralStorages:
## nginx temporary files (/tmp)
tmp:
sizeLimit: 10Mi
medium: Memory
elementWeb:
enabled: true
## Arbitrary extra config to inject into Element Web's config.json.
## Each key under additional is an additional config to merge into Element Web's config.json.
##
## Full details on available configuration options can be found at https://github.com/element-hq/element-web/blob/develop/docs/config.md
## Most settings are configurable but some settings are owned by the chart and can't be overwritten
additional: {}
# Number of Element Web replicas to start up
replicas: 1
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: oci.element.io
## The path in the registry where the container image is located
repository: element-web
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "v1.12.34"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Configuration of the Service handling inbound HTTP(S) traffic for this component.
## Takes precedence over `ingress.service` and the global `httpService`. Leave empty to inherit `httpService`.
# httpService:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
httpService: {}
## How this ingress should be constructed
ingress:
## What hostname should be used for this Ingress
# host:
## Annotations to be added to this Ingress
annotations: {}
## What Ingress Class Name that should be used for this Ingress
# className:
## Disable TLS configuration by setting it to false
tlsEnabled: true
## The name of the Secret containing the TLS certificate and the key that should be used for this Ingress
# tlsSecret:
## Optional Service override for this Ingress.
## When a field is set, it overrides `httpService`. `<component>.httpService` takes precedence over this.
# service:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
service: {}
## If set, some tweaks will be applied automatically to ingresses based on the controller type here.
## This can be set to `ingress-nginx`.
# controllerType:
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in Element Web, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Element Web, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Element Web, as a yaml array
extraInitContainers: []
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10004
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10004
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10004
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 50m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 200Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## How long, in seconds, each container of this workload waits before stopping when it rolls out
## This gives the Service time to update its iptables rules before the pod is killed
## Unset this to stop the containers without waiting
preStopSleepSeconds: 3
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 3
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 4
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 3
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configures sizeLimit (maximum size) and medium for this component's emptyDir volumes.
## Each sizeLimit is a Kubernetes quantity string, e.g. 10Mi.
## medium is either "Memory" (tmpfs-backed) or "" (node default storage).
ephemeralStorages:
## nginx temporary files (/tmp)
tmp:
sizeLimit: 10Mi
medium: Memory
haproxy:
replicas: 1
## How long HAProxy keeps its listeners open after the pod starts stopping, e.g. 5s
## This gives the Service time to update its iptables rules before the pod is killed
grace: 5s
## How long at most HAProxy takes to fully stop after the pod starts stopping, e.g. 10s
## HAProxy closes every remaining connection when this time is up
## Keep this + `grace` below the pod's terminationGracePeriodSeconds, which defaults to 30s
hardStopAfter: 10s
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: docker.io
## The path in the registry where the container image is located
repository: library/haproxy
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "3.4.8-alpine"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in HAProxy, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in HAProxy, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to HAProxy, as a yaml array
extraInitContainers: []
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10001
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10001
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10001
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 100Mi
cpu: 100m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 200Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Whether to deploy ServiceMonitors into the cluster for this component
## Requires the ServiceMonitor CRDs to be in the cluster
serviceMonitors:
enabled: true
## List of RelabelConfig's to apply to the target before scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
relabelings: []
## List of RelabelConfig's to apply to the samples before ingestion but after scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
metricRelabelings: []
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 5
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 5
# The failureThreshold here is tweaked towards Synapse being ready
# If Synapse isn't being deployed, unsetting this or setting it to 3 maybe more appropriate
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 150
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
hookshot:
enabled: false
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: ghcr.io
## The path in the registry where the container image is located
repository: matrix-org/matrix-hookshot
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "7.6.2"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
# Hookshot encryption support is experimental. You can enable it by setting `enableEncryption` to `true`.
enableEncryption: false
user:
localpart: hookshot
logging:
# The maximum level of Hookshot log output before any overrides
# Must be one of [critical, error, warning, info, debug]
level: info
# Use 0 replicas to stop Hookshot
replicas: 1
## Hookshot registration file to connect to a remote Synapse instance.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## appserviceRegistration:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## appserviceRegistration:
## secret: existing-secret
## secretKey: key-in-secret
# appserviceRegistration: {}
## Hookshot passkey used to encrypt stored tokens.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## passkey:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## passkey:
## secret: existing-secret
## secretKey: key-in-secret
# passkey: {}
## Details of the external Redis/Valkey to use
## Does not need to be set if the internal Valkey should be used
## This is useful for production environments where you want to use
## managed Redis/Valkey services (AWS Elasticache, Azure Cache for Redis, etc.)
# redisOrValkey:
## Redis/Valkey host
# host:
## Redis/Valkey port
# port: 6379
## Redis/Valkey database number (0-15)
# db: 0
## Redis/Valkey password (optional - many managed services require auth).
## It can either be provided inline in the Helm chart e.g.:
## password:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## password:
## secret: existing-secret
## secretKey: key-in-secret
# password: {}
## Enable TLS for Redis/Valkey connection
# tls: false
## Configuration of the Service handling inbound HTTP(S) traffic for this component.
## Takes precedence over `ingress.service` and the global `httpService`. Leave empty to inherit `httpService`.
# httpService:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
httpService: {}
## How this ingress should be constructed
ingress:
## What hostname should be used for this Ingress
# host:
## Annotations to be added to this Ingress
annotations: {}
## What Ingress Class Name that should be used for this Ingress
# className:
## Disable TLS configuration by setting it to false
tlsEnabled: true
## The name of the Secret containing the TLS certificate and the key that should be used for this Ingress
# tlsSecret:
## Optional Service override for this Ingress.
## When a field is set, it overrides `httpService`. `<component>.httpService` takes precedence over this.
# service:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
service: {}
## If set, some tweaks will be applied automatically to ingresses based on the controller type here.
## This can be set to `ingress-nginx`.
# controllerType:
## Additional configuration to provide to Hookshot.
## You can, if you whish, override it in the additional config.
## Each key under additional is an additional config to merge into Hookshot hookshot-config.yaml
## Full details on available configuration options can be found at https://matrix-org.github.io/matrix-hookshot/latest/setup.html
## This can be provided in-line in the Helm Chart and/or via an existing Secret
## e.g.
## additional:
## 0-customConfig:
## config: |
## <any valid configuration>
## 1-customConfig:
## configSecret: custom-config
## configSecretKey: shared.yaml
##
## Most settings are configurable but some settings are owned by the chart and can't overwritten
additional: {}
## Configures the PersistentVolumeClaim to be used for storage
storage:
## Name of an existing PersistentVolumeClaim in this namespace that should be used
# existingClaim:
## The size of a PersistentVolumeClaim to be constructed
## Ignored if existingClaim is provided
size: 10Gi
## The PersistentVolumeClaim PV selector
# selector: {}
## The PersistentVolumeClaim PV name
# volumeName:
## The StorageClass to be used by the constructed PersistentVolumeClaim.
## The top-level storage.storageClassName value is used, if not provided (or the cluster default if neither are provided).
## If changed after initial usage the PersistentVolumeClaim could be recreated causing data-loss.
## Ignored if existingClaim is provided
# storageClassName:
## Whether to instruct Helm to keep or delete the constructed PersistentVolumeClaim when uninstalling the chart
## The top-level storage.resourcePolicy value is used, if not provided.
## Ignored if existingClaim is provided.
# resourcePolicy: keep
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 100Mi
cpu: 10m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 1000Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
# Extra volumes to mount in Hookshot, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Hookshot, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Hookshot, as a yaml array
extraInitContainers: []
## Labels to add to all manifest for this component
labels: {}
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10007
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10007
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10007
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Set DNS policy for the pod. Kubernetes defaults to ClusterFirst if no value is provided here
dnsPolicy: ""
## Pod-level DNS configuration. Only effective when dnsPolicy is set to "None".
dnsConfig: {}
## Defines the annotations to add to the workload
# annotations: {}
## Whether to deploy ServiceMonitors into the cluster for this component
## Requires the ServiceMonitor CRDs to be in the cluster
serviceMonitors:
enabled: true
## List of RelabelConfig's to apply to the target before scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
relabelings: []
## List of RelabelConfig's to apply to the samples before ingestion but after scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
metricRelabelings: []
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
## The list of hosts aliases to configure on the pod spec.
## It should be avoid as much as possible to use this feature.
## Please prefer using an DNS entry to resolve your hostnames.
## This can be used as a workaround when entries cannot be resolved using DNS, for example for our automated testings.
## e.g.
## hostAliases:
## - ip: 192.0.2.1 # An IP resolution to add to /etc/hosts
## # A list of hostnames to be associated with the above IP
## hostnames:
## - ess.localhost
## - synapse.ess.localhost
hostAliases: []
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 9
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 9
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 9
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configures sizeLimit (maximum size) and medium for this component's emptyDir volumes.
## Each sizeLimit is a Kubernetes quantity string, e.g. 10Mi.
## medium is either "Memory" (tmpfs-backed) or "" (node default storage).
ephemeralStorages:
## temporary files (/tmp)
tmp:
sizeLimit: 10Mi
medium: Memory
matrixAuthenticationService:
enabled: true
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: oci.element.io
## The path in the registry where the container image is located
repository: matrix-authentication-service
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "1.29.0"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
replicas: 1
## Details of the external Postgres Database to use
## Does not need to be set if postgres.enabled=True
# postgres:
## PostgreSQL database host
# host:
## PostgreSQL port
# port: 5432
## PostgreSQL username
# user:
## PostgreSQL database name
# database:
## TLS settings to use for the PostgreSQL connection
# sslMode: prefer
## PostgreSQL password.
## It can either be provided inline in the Helm chart e.g.:
## password:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## password:
## secret: existing-secret
## secretKey: key-in-secret
# password: {}
## Encryption secret.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## encryptionSecret:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## encryptionSecret:
## secret: existing-secret
## secretKey: key-in-secret
# encryptionSecret: {}
## Synapse - MAS Shared Secret.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## synapseSharedSecret:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## synapseSharedSecret:
## secret: existing-secret
## secretKey: key-in-secret
# synapseSharedSecret: {}
## Additional configuration to provide to Matrix Authentication Service.
## Each key under additional is an additional config to merge into Matrix Authentication Service mas-config.yaml
## Full details on available configuration options can be found at https://element-hq.github.io/matrix-authentication-service/reference/configuration.html
## This can be provided in-line in the Helm Chart and/or via an existing Secret
## e.g.
## additional:
## 0-customConfig:
## config: |
## <any valid configuration>
## 1-customConfig:
## configSecret: custom-config
## configSecretKey: shared.yaml
##
## Most settings are configurable but some settings are owned by the chart and can't overwritten
additional: {}
privateKeys: {}
## RSA Private Key.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## rsa:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## rsa:
## secret: existing-secret
## secretKey: key-in-secret
# rsa: {}
## ECDSA Prime256v1 Private Key.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## ecdsaPrime256v1:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## ecdsaPrime256v1:
## secret: existing-secret
## secretKey: key-in-secret
# ecdsaPrime256v1: {}
## ECDSA Secp256k1 Private Key.
## It can either be provided inline in the Helm chart e.g.:
## ecdsaSecp256k1:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## ecdsaSecp256k1:
## secret: existing-secret
## secretKey: key-in-secret
# ecdsaSecp256k1: {}
## ECDSA Secp384r1 Private Key.
## It can either be provided inline in the Helm chart e.g.:
## ecdsaSecp384r1:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## ecdsaSecp384r1:
## secret: existing-secret
## secretKey: key-in-secret
# ecdsaSecp384r1: {}
## Configuration of the Service handling inbound HTTP(S) traffic for this component.
## Takes precedence over `ingress.service` and the global `httpService`. Leave empty to inherit `httpService`.
# httpService:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
httpService: {}
## How this ingress should be constructed
ingress:
## What hostname should be used for this Ingress
# host:
## Annotations to be added to this Ingress
annotations: {}
## What Ingress Class Name that should be used for this Ingress
# className:
## Disable TLS configuration by setting it to false
tlsEnabled: true
## The name of the Secret containing the TLS certificate and the key that should be used for this Ingress
# tlsSecret:
## Optional Service override for this Ingress.
## When a field is set, it overrides `httpService`. `<component>.httpService` takes precedence over this.
# service:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
service: {}
## If set, some tweaks will be applied automatically to ingresses based on the controller type here.
## This can be set to `ingress-nginx`.
# controllerType:
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 50m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 350Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Labels to add to all manifest for this component
labels: {}
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## The list of hosts aliases to configure on the pod spec.
## It should be avoid as much as possible to use this feature.
## Please prefer using an DNS entry to resolve your hostnames.
## This can be used as a workaround when entries cannot be resolved using DNS, for example for our automated testings.
## e.g.
## hostAliases:
## - ip: 192.0.2.1 # An IP resolution to add to /etc/hosts
## # A list of hostnames to be associated with the above IP
## hostnames:
## - ess.localhost
## - synapse.ess.localhost
hostAliases: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10005
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10005
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10005
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Set DNS policy for the pod. Kubernetes defaults to ClusterFirst if no value is provided here
dnsPolicy: ""
## Pod-level DNS configuration. Only effective when dnsPolicy is set to "None".
dnsConfig: {}
## Defines the annotations to add to the workload
# annotations: {}
## Whether to deploy ServiceMonitors into the cluster for this component
## Requires the ServiceMonitor CRDs to be in the cluster
serviceMonitors:
enabled: true
## List of RelabelConfig's to apply to the target before scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
relabelings: []
## List of RelabelConfig's to apply to the samples before ingestion but after scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
metricRelabelings: []
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in Matrix Authentication Service, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Matrix Authentication Service, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Matrix Authentication Service, as a yaml array
extraInitContainers: []
## How long, in seconds, each container of this workload waits before stopping when it rolls out
## This gives the Service time to update its iptables rules before the pod is killed
## Unset this to stop the containers without waiting
preStopSleepSeconds: 3
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 4
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Enables synapse to Matrix Authentication Service migration
## The migration process must follow the following steps:
## 1. Set `matrixAuthenticationService.enabled: true` and `matrixAuthenticationService.syn2mas.enable: true`, run the helm upgrade command, check the result of the pre-upgrade hook job
## 2. Set `matrixAuthenticationService.syn2mas.dryRun`: false, run the helm upgrade command, check the result of the pre-upgrade hook job
## 3. Set `matrixAuthenticationService.syn2mas.enabled: false` to disable syn2mas and allow running `helm upgrade` again.
##
## If `deploymentMarkers` are enabled, following the steps above will cause the following `MATRIX_STACK_MSC3861` marker transitions :
## 1. Stay on `legacy_auth`
## 2. `legacy_auth` -> `syn2mas_migrated`
## 3. `syn2mas_migrated` -> `delegated_auth`
## The marker will effectively prevent :
## - Running syn2mas migration again after it has run successfully and is in `syn2mas_migrated` state
## - Downgrading from `syn2mas_migrated`/`delegated_auth` to `legacy_auth`
syn2mas:
enabled: false
# Syn2Mas relies on the debug image to copy mas-cli to the matrix-tools container
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: oci.element.io
## The path in the registry where the container image is located
repository: matrix-authentication-service
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "1.29.0-debug"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10005
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10005
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10005
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 50m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 350Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in Syn2Mas, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Syn2Mas, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Syn2Mas, as a yaml array
extraInitContainers: []
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## Configures sizeLimit (maximum size) and medium for this component's emptyDir volumes.
## Each sizeLimit is a Kubernetes quantity string, e.g. 10Mi.
## medium is either "Memory" (tmpfs-backed) or "" (node default storage).
ephemeralStorages:
## temporary mas-cli copy (/tmp-mas-cli)
tmpMasCli:
sizeLimit: 100Mi
medium: Memory
## Runs the syn2mas process in dryRun mode.
## Force the authentication to happen with legacy authentication.
## This can be used to deploy Matrix Authentication Service and keeping auth on Synapse.
## This must be set to false and never switch again after the migration to MAS has been run or the deployment markers hooks will prevent redeploying.
dryRun: true
## Lets the syn2mas process proceed when its preflight check only reports warnings
## (for example guest accounts or non-email third-party identifiers).
## Warnings are fatal by default: review them in the job logs before enabling this.
acceptWarnings: false
postgres:
enabled: true
postgresExporter:
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: ghcr.io
## The path in the registry where the container image is located
repository: prometheus-community/postgres-exporter
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "v0.21.1"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 10Mi
cpu: 10m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 500Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
# Extra volumes to mount in PostgresExporter, as a yaml array
extraVolumeMounts: []
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 20
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Postgres Admin Password.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## adminPassword:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## adminPassword:
## secret: existing-secret
## secretKey: key-in-secret
# adminPassword: {}
# Use 0 replicas to stop Postgres
replicas: 1
essPasswords: {}
## Synapse DB Password.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## synapse:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## synapse:
## secret: existing-secret
## secretKey: key-in-secret
# synapse: {}
## Matrix Authentication Service DB Password.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## matrixAuthenticationService:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## matrixAuthenticationService:
## secret: existing-secret
## secretKey: key-in-secret
# matrixAuthenticationService: {}
## Configures the PersistentVolumeClaim to be used for storage
storage:
## Name of an existing PersistentVolumeClaim in this namespace that should be used
# existingClaim:
## The size of a PersistentVolumeClaim to be constructed
## Ignored if existingClaim is provided
size: 10Gi
## The PersistentVolumeClaim PV selector
# selector: {}
## The PersistentVolumeClaim PV name
# volumeName:
## The StorageClass to be used by the constructed PersistentVolumeClaim.
## The top-level storage.storageClassName value is used, if not provided (or the cluster default if neither are provided).
## If changed after initial usage the PersistentVolumeClaim could be recreated causing data-loss.
## Ignored if existingClaim is provided
# storageClassName:
## Whether to instruct Helm to keep or delete the constructed PersistentVolumeClaim when uninstalling the chart
## The top-level storage.resourcePolicy value is used, if not provided.
## Ignored if existingClaim is provided.
# resourcePolicy: keep
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: docker.io
## The path in the registry where the container image is located
repository: postgres
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "17.12-alpine"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in Postgres, as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in Postgres, as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Postgres, as a yaml array
extraInitContainers: []
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10091
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10091
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10091
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 100Mi
cpu: 100m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 4Gi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Whether to deploy ServiceMonitors into the cluster for this component
## Requires the ServiceMonitor CRDs to be in the cluster
serviceMonitors:
enabled: true
## List of RelabelConfig's to apply to the target before scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
relabelings: []
## List of RelabelConfig's to apply to the samples before ingestion but after scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
metricRelabelings: []
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configures sizeLimit (maximum size) and medium for this component's emptyDir volumes.
## Each sizeLimit is a Kubernetes quantity string, e.g. 10Mi.
## medium is either "Memory" (tmpfs-backed) or "" (node default storage).
ephemeralStorages:
## temporary files (/tmp)
tmp:
sizeLimit: 10Mi
medium: Memory
## postgresql runtime directory (/var/run)
varRun:
sizeLimit: 1Mi
medium: Memory
valkey:
# redis maxmemory and maxmemory-policy settings. See https://redis.io/docs/latest/develop/reference/eviction/
# This value should be updated with changes to Valkey's memory requests and limits below
maxMemory: 40mb
maxMemoryPolicy: allkeys-lru
# Use 0 replicas to stop Valkey
replicas: 1
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: docker.io
## The path in the registry where the container image is located
repository: valkey/valkey
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "9.1.4-alpine"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
# Extra volumes to mount in , as a yaml array
# This supports helm templating
extraVolumes: []
# Extra volumes to mount in , as a yaml array
extraVolumeMounts: []
# Extra initContainers to add to Valkey, as a yaml array
extraInitContainers: []
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10002
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10002
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10002
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 50m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 50Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Whether to deploy ServiceMonitors into the cluster for this component
## Requires the ServiceMonitor CRDs to be in the cluster
serviceMonitors:
enabled: true
## List of RelabelConfig's to apply to the target before scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
relabelings: []
## List of RelabelConfig's to apply to the samples before ingestion but after scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
metricRelabelings: []
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 5
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 10
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
valkeyExporter:
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: ghcr.io
## The path in the registry where the container image is located
repository: oliver006/redis_exporter
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "v1.97.0"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 10Mi
cpu: 10m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 50Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
# Extra volumes to mount in Valkey Exporter, as a yaml array
extraVolumeMounts: []
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 20
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
# Temporarily left for backwards compatibility with existing installations that override values here but the charts now sets no defaults
# Everything will come from Valkey
redis: {}
synapse:
enabled: true
## A hook job will make sure that Synapse config is valid before continuing
checkConfigHook:
enabled: true
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 50Mi
cpu: 50m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 200Mi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Details of the external Postgres Database to use
## Does not need to be set if postgres.enabled=True
# postgres:
## PostgreSQL database host
# host:
## PostgreSQL port
# port: 5432
## PostgreSQL username
# user:
## PostgreSQL database name
# database:
## TLS settings to use for the PostgreSQL connection
# sslMode: prefer
## PostgreSQL password.
## It can either be provided inline in the Helm chart e.g.:
## password:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## password:
## secret: existing-secret
## secretKey: key-in-secret
# password: {}
## Configures the media store for Synapse
media:
## Configures the PersistentVolumeClaim to be used for storage
storage:
## Name of an existing PersistentVolumeClaim in this namespace that should be used
# existingClaim:
## The size of a PersistentVolumeClaim to be constructed
## Ignored if existingClaim is provided
size: 10Gi
## The PersistentVolumeClaim PV selector
# selector: {}
## The PersistentVolumeClaim PV name
# volumeName:
## The StorageClass to be used by the constructed PersistentVolumeClaim.
## The top-level storage.storageClassName value is used, if not provided (or the cluster default if neither are provided).
## If changed after initial usage the PersistentVolumeClaim could be recreated causing data-loss.
## Ignored if existingClaim is provided
# storageClassName:
## Whether to instruct Helm to keep or delete the constructed PersistentVolumeClaim when uninstalling the chart
## The top-level storage.resourcePolicy value is used, if not provided.
## Ignored if existingClaim is provided.
# resourcePolicy: keep
## Configures sizeLimit (maximum size) and medium for this component's emptyDir volumes.
## Each sizeLimit is a Kubernetes quantity string, e.g. 10Mi.
## medium is either "Memory" (tmpfs-backed) or "" (node default storage).
ephemeralStorages:
## media tmp directory, used to upload files larger than 100KB
tmp:
sizeLimit: 1Gi
medium: Memory
## The maximum size (in bytes ending in M or K) that Synapse will accept for media uploads
## You may need to adjust your ingress controller to also allow uploads of this size
## You may also need to adjust your synapse.media.ephemeralStorages.tmp directory sizeLimit to support buffering of large upload files
maxUploadSize: 100M
## Key used to sign events and federation requests.
## This needs to be the full signing key starting `ed25519 ...`.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## signingKey:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## signingKey:
## secret: existing-secret
## secretKey: key-in-secret
# signingKey: {}
## Shared Secret to registering users without having any users provisioned.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## registrationSharedSecret:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## registrationSharedSecret:
## secret: existing-secret
## secretKey: key-in-secret
# registrationSharedSecret: {}
## Secret used to sign Synapse issued tokens.
## This secret is optional, and will be generated by the `initSecrets` job
## if it is empty.
## It can either be provided inline in the Helm chart e.g.:
## macaroon:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## macaroon:
## secret: existing-secret
## secretKey: key-in-secret
# macaroon: {}
## Details of the external Redis/Valkey to use
## Does not need to be set if the internal Valkey should be used
## This is useful for production environments where you want to use
## managed Redis/Valkey services (AWS Elasticache, Azure Cache for Redis, etc.)
# redisOrValkey:
## Redis/Valkey host
# host:
## Redis/Valkey port
# port: 6379
## Redis/Valkey database number (0-15)
# db: 0
## Redis/Valkey password (optional - many managed services require auth).
## It can either be provided inline in the Helm chart e.g.:
## password:
## value: SecretValue
##
## Or it can be provided via an existing Secret e.g.:
## password:
## secret: existing-secret
## secretKey: key-in-secret
# password: {}
## Enable TLS for Redis/Valkey connection
# tls: false
## Additional configuration to provide to all Synapse processes.
## Each key under additional is an additional config to merge into synapse homeserver.yaml
## Full details on available configuration options can be found at https://element-hq.github.io/synapse/latest/usage/configuration/config_documentation.html
## This can be provided in-line in the Helm Chart and/or via an existing Secret
## e.g.
## additional:
## 0-customConfig:
## config: |
## <any valid configuration>
## 1-customConfig:
## configSecret: custom-config
## configSecretKey: shared.yaml
##
## Most settings are configurable but some settings are owned by the chart and can't overwritten
additional: {}
## Details of Application Service registration files to give to Synapse
## e.g.
## appservices:
## - configMap: test-appservice
## configMapKey: registration.yaml
## - secret: test-appservice
## secretKey: registration.yaml
appservices: []
## Additional Synapse processes managed by this chart
## e.g.
## workers:
## client-reader:
## enabled: true
## replicas: 2
## event-creator:
## enabled: true
workers:
account-data:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
appservice:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
background:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
client-reader:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
device-lists:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
encryption:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
event-creator:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
event-persister:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
federation-inbound:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
federation-reader:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
federation-sender:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
initial-synchrotron:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
mas-helper:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
media-repository:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
presence-writer:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
push-rules:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
pusher:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
receipts:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
sliding-sync:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
sso-login:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
synchrotron:
## Set to true to deploy this worker
enabled: false
## The number of replicas of this worker to run
replicas: 1
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 3
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 21
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
typing-persister:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
user-dir:
## Set to true to deploy this worker
enabled: false
## Resources for this worker.
## If omitted the global Synapse resources are used
# resources: {}
## Use 0 replicas to stop the worker without removing routing to it
replicas: 1
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 2
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Synapse's logging settings
logging:
## The maximum level of Synapse log output before any overrides
rootLevel: INFO
## Override the log level of specific loggers
## e.g.
## levelOverrides:
## synapse.util.caches.lrucache: WARNING
levelOverrides: {}
# Use 0 replicas to stop Synapse main process without removing routing to it
replicas: 1
# Details of the image to be used
image:
## The host and (optional) port of the container image registry for this component.
## If not specified Docker Hub is implied
registry: oci.element.io
## The path in the registry where the container image is located
repository: synapse
## The tag of the container image to use.
## One of tag or digest must be provided.
tag: "v1.165.0"
## Container digest to use. Used to pull the image instead of the image tag if set
## The tag will still be set as the app.kubernetes.io/version label
# digest:
## Whether the image should be pulled on container startup. Valid values are Always, IfNotPresent and Never
## If this isn't provided it defaults to Always when using the image tag or IfNotPresent if using a digest
# pullPolicy:
## A list of pull secrets to use for this image
## e.g.
## pullSecrets:
## - name: dockerhub
pullSecrets: []
# Extra volumes to mount in Synapse, as a yaml array
# This supports helm templating
# For each extra volume, specify `mountContext` to `hook`, `runtime` or `both` to specify
# if it has to be mounted in hook jobs, runtime only, or both.
# Defaults to "both".
extraVolumes: []
# Extra volumes to mount in Synapse, as a yaml array
# For each extra volume mount, specify `mountContext` to `hook`, `runtime` or `both` to specify
# if it has to be mounted in hook jobs, runtime only, or both.
# Defaults to "both".
extraVolumeMounts: []
# Extra initContainers to add to Synapse, as a yaml array
extraInitContainers: []
## Configuration of the Service handling inbound HTTP(S) traffic for this component.
## Takes precedence over `ingress.service` and the global `httpService`. Leave empty to inherit `httpService`.
# httpService:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
httpService: {}
## How this ingress should be constructed
ingress:
## What hostname should be used for this Ingress
# host:
## Annotations to be added to this Ingress
annotations: {}
## What Ingress Class Name that should be used for this Ingress
# className:
## Disable TLS configuration by setting it to false
tlsEnabled: true
## The name of the Secret containing the TLS certificate and the key that should be used for this Ingress
# tlsSecret:
## Optional Service override for this Ingress.
## When a field is set, it overrides `httpService`. `<component>.httpService` takes precedence over this.
# service:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
service: {}
## If set, some tweaks will be applied automatically to ingresses based on the controller type here.
## This can be set to `ingress-nginx`.
# controllerType:
## Labels to add to all manifest for this component
labels: {}
## Defines the annotations to add to the workload
# annotations: {}
## A subset of SecurityContext. ContainersSecurityContext holds pod-level security attributes and common container settings
containersSecurityContext:
## Controls whether a process can gain more privileges than its parent process.
## This bool directly controls whether the no_new_privs flag gets set on the container process.
## allowPrivilegeEscalation is always true when the container is run as privileged, or has CAP_SYS_ADMIN
allowPrivilegeEscalation: false
## Whether the container should be run in privileged mode.
## Processes in privileged containers are essentially equivalent to root on the host.
## Do not set to true without good reason.
privileged: false
## Give a process some privileges, but not all the privileges of the root user.
capabilities:
## Privileges to add.
# add: []
## Privileges to drop.
drop:
- ALL
## Mounts the container's root filesystem as read-only.
readOnlyRootFilesystem: true
## To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile. Valid options for type include RuntimeDefault, Unconfined, and Localhost.
## localhostProfile must only be set set if type Localhost. It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
# seccompProfile:
# type: RuntimeDefault
## Set DNS policy for the pod. Kubernetes defaults to ClusterFirst if no value is provided here
dnsPolicy: ""
## Pod-level DNS configuration. Only effective when dnsPolicy is set to "None".
dnsConfig: {}
## Defines additional environment variables to be injected onto this workload
## e.g.
## extraEnv:
## - name: FOO
## value: "bar"
extraEnv: []
## The list of hosts aliases to configure on the pod spec.
## It should be avoid as much as possible to use this feature.
## Please prefer using an DNS entry to resolve your hostnames.
## This can be used as a workaround when entries cannot be resolved using DNS, for example for our automated testings.
## e.g.
## hostAliases:
## - ip: 192.0.2.1 # An IP resolution to add to /etc/hosts
## # A list of hostnames to be associated with the above IP
## hostnames:
## - ess.localhost
## - synapse.ess.localhost
hostAliases: []
## NodeSelector is a selector which must be true for the pod to fit on a node.
## The Selector which must match a node's labels for the pod to be scheduled on that node.
## More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
## Overrides the global nodeSelector if specified
nodeSelector: {}
## If specified, indicates the pod's priority and must reference the name of an existing PriorityClass object.
## "system-cluster-critical" and "system-node-critical" are two special built-in classes indicating the highest priorities.
## If not set (empty), the pod's priority defaults to the cluster's globalDefault PriorityClass or zero.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
priorityClassName: ""
## If specified, the pod will be dispatched by the specified scheduler.
## If not specified, the pod will be dispatched by the default scheduler.
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
schedulerName: ""
## If specified, refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod.
## If not set or empty, the default RuntimeClass is used, which is equivalent to the behavior when this feature is disabled.
## More info: https://kubernetes.io/docs/concepts/containers/runtime-class/
runtimeClassName: ""
## If specified, the pod's scheduling constraints, configured independently per affinity type.
## Each affinity type set here overrides only the matching global affinity type for this component; the other types are still inherited from the global affinity.
## A type is inherited from the global affinity while left unset here; set a type to {} to blank out the inherited global value for that type, e.g.:
## nodeAffinity: {} ## override, or with {} blank out, the global nodeAffinity for this component
## podAffinity: {} ## override, or with {} blank out, the global podAffinity for this component
## podAntiAffinity: {} ## override, or with {} blank out, the global podAntiAffinity for this component
## More info: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## A subset of PodSecurityContext. PodSecurityContext holds pod-level security attributes and common container settings
podSecurityContext:
## A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to
## change the ownership of that volume to be owned by the pod:
##
## 1. The owning GID will be the FSGroup
## 2. The setgid bit is set (new files created in the volume will be owned by FSGroup)## 3. The permission bits are OR'd with rw-rw----
##
## If unset, the Kubelet will not modify the ownership and permissions of any volume.
fsGroup: 10091
## fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod.
## This field will only apply to volume types which support fsGroup based ownership(and permissions).
## It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used.
# fsGroupChangePolicy:
## The GID to run the entrypoint of the container process. Uses runtime default if unset.
runAsGroup: 10091
## Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed.
runAsNonRoot: true
## The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified.
runAsUser: 10091
## SELinuxOptions are the labels to be applied to all the pod containers
# seLinuxOptions:
## Level is SELinux level label that applies to the container.
# level:
## Role is a SELinux role label that applies to the container.
# role:
## Type is a SELinux type label that applies to the container.
# type:
## User is a SELinux user label that applies to the container.
# user:
## "To set the Seccomp profile for a Container, include the seccompProfile field in the securityContext section of your Pod or Container manifest.
## The seccompProfile field is a SeccompProfile object consisting of type and localhostProfile.
## Valid options for type include RuntimeDefault, Unconfined, and Localhost. localhostProfile must only be set set if type Localhost.
## It indicates the path of the pre-configured profile on the node, relative to the kubelet's configured Seccomp profile location (configured with the --root-dir flag).
seccompProfile:
# localhostProfile:
type: RuntimeDefault
## A list of groups applied to the first process run in each container, in addition to the container's primary GID.
## If unspecified, no groups will be added to any container.
supplementalGroups: []
## Kubernetes resources to allocate to each instance.
resources:
## Requests describes the minimum amount of compute resources required. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
requests:
memory: 100Mi
cpu: 100m
## No ephemeral-storage requests by default
# ephemeral-storage:
## Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
limits:
memory: 4Gi
## No CPU or ephemeral-storage limits by default
# cpu:
# ephemeral-storage:
## Configures sizeLimit (maximum size) and medium for this component's emptyDir volumes.
## Each sizeLimit is a Kubernetes quantity string, e.g. 10Mi.
## medium is either "Memory" (tmpfs-backed) or "" (node default storage).
ephemeralStorages:
## non-media tmp directory. See synapse.media.ephemeralStorages.tmp for tmp directory for media uploads
nonMediaTmp:
sizeLimit: 10Mi
medium: Memory
## Controls configuration of the ServiceAccount for this component
serviceAccount:
## Whether a ServiceAccount should be created by the chart or not
create: true
## What name to give the ServiceAccount. If not provided the chart will provide the name automatically
name: ""
## Annotations to add to the service account
annotations: {}
## Whether to deploy ServiceMonitors into the cluster for this component
## Requires the ServiceMonitor CRDs to be in the cluster
serviceMonitors:
enabled: true
## List of RelabelConfig's to apply to the target before scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
relabelings: []
## List of RelabelConfig's to apply to the samples before ingestion but after scraping
## see https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
metricRelabelings: []
## Workload tolerations allows Pods that are part of this (sub)component to 'tolerate' any taint that matches the triple <key,value,effect> using the matching operator <operator>.
##
## * effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
## * key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
## * operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
## * value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
##
## * tolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
## e.g.
## tolerations:
## - effect:
## key:
## operator:
## value:
tolerations: []
## TopologySpreadConstraints describes how Pods for this component should be spread between nodes.
## https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ for in-depth details
## labelSelector & whenUnsatisfiable can be omitted and the chart will populate a sensible value for this component.
## Similarly `pod-template-hash` will be aded to `matchLabelKeys` if appropriate for this component.
## If any TopologySpreadConstraints are provided for a component any global TopologySpreadConstraints are ignored for that component.
## e.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: topology.kubernetes.io/zone
## # nodeAffinityPolicy: Honor/Ignore
## # nodeTaintsPolicy: Honor/Ignore
## # whenUnsatisfiable: DoNotSchedule/ScheduleAnyway
topologySpreadConstraints: []
## How long, in seconds, each container of this workload waits before stopping when it rolls out
## This gives the Service time to update its iptables rules before the pod is killed
## Unset this to stop the containers without waiting
preStopSleepSeconds: 3
## Configuration of the thresholds and frequencies of the livenessProbe
livenessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 6
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 12
## Configuration of the thresholds and frequencies of the readinessProbe
readinessProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 8
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 2
## Number of seconds after which the probe times out
timeoutSeconds: 12
## Configuration of the thresholds and frequencies of the startupProbe
startupProbe:
## How many consecutive failures for the probe to be considered failed
failureThreshold: 54
## Number of seconds after the container has started before the probe starts
initialDelaySeconds: 0
## How often (in seconds) to perform the probe
periodSeconds: 2
## How many consecutive successes for the probe to be consider successful after having failed
successThreshold: 1
## Number of seconds after which the probe times out
timeoutSeconds: 1
## Extra command line arguments to provide to Synapse
extraArgs: []
wellKnownDelegation:
enabled: true
## Labels to add to all manifest for this component
labels: {}
## Configuration of the Service handling inbound HTTP(S) traffic for this component.
## Takes precedence over `ingress.service` and the global `httpService`. Leave empty to inherit `httpService`.
# httpService:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
httpService: {}
## How this ingress should be constructed
ingress:
## What hostname should be used for this Ingress
# host:
## Annotations to be added to this Ingress
annotations: {}
## What Ingress Class Name that should be used for this Ingress
# className:
## Disable TLS configuration by setting it to false
tlsEnabled: true
## The name of the Secret containing the TLS certificate and the key that should be used for this Ingress
# tlsSecret:
## Optional Service override for this Ingress.
## When a field is set, it overrides `httpService`. `<component>.httpService` takes precedence over this.
# service:
# type: ClusterIP
# annotations: {}
# # External traffic policy will be configured on services of type `NodePort` and `LoadBalancer`
# externalTrafficPolicy: Cluster
# internalTrafficPolicy: Cluster
# # External IPs addresses of this service.
# externalIPs: []
service: {}
## If set, some tweaks will be applied automatically to ingresses based on the controller type here.
## This can be set to `ingress-nginx`.
# controllerType:
## If ElementWeb is deployed, the base domain will redirect to it's ingress host by default
## If ElementWeb is not deployed or this is disabled, no base domain URL redirect will be set.
baseDomainRedirect:
enabled: true
## You can override with another redirect URL here.
url: ""
## Additional configuration to provide to all WellKnown static file
## Configuration should be provided as JSON strings
additional:
client: "{}"
server: "{}"
support: "{}"
## Headers to return on the /.well-known/matrix/* responses
## Additional headers can be added and the default headers can be
## modified or removed (by setting their value to null)
headers:
Access-Control-Allow-Headers: "X-Requested-With, Content-Type, Authorization"
Access-Control-Allow-Methods: "GET, POST, PUT, DELETE, OPTIONS"
Access-Control-Allow-Origin: "*"
Cache-Control: "public, max-age=3600"
Content-Security-Policy: "frame-ancestors 'self'"
X-Content-Type-Options: "nosniff"
X-Frame-Options: "SAMEORIGIN"
X-Robots-Tag: "noindex, nofollow, noarchive, noimageindex"
X-XSS-Protection: "1; mode=block"