Files
mailhog/values.yaml
Conan Scott 2cc97e5b98
Some checks failed
Helm Publish / publish (push) Failing after 2m19s
configured ingress
2025-12-12 22:45:45 +11:00

148 lines
3.4 KiB
YAML

image:
repository: docker.io/mailhog/mailhog
tag: ""
pullPolicy: IfNotPresent
imagePullSecrets: []
extraContainers: []
nameOverride: ""
fullnameOverride: ""
containerPort:
http:
name: http
port: 8025
smtp:
name: tcp-smtp
port: 1025
serviceAccount:
# Specifies whether a ServiceAccount should be created
create: true
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name: ""
# Image pull secrets that are attached to the ServiceAccount
imagePullSecrets: []
automountServiceAccountToken: false
service:
annotations: {}
extraPorts: []
clusterIP: ""
externalIPs: []
loadBalancerIP: ""
loadBalancerSourceRanges: []
type: ClusterIP
# Named target ports are not supported by GCE health checks, so when deploying on GKE
# and exposing it via GCE ingress, the health checks fail and the load balancer returns a 502.
namedTargetPort: true
port:
http: 8025
smtp: 1025
nodePort:
http: ""
smtp:
""
#securityContext:
#runAsUser: 1000
#runAsGroup: 1000
#runAsNonRoot: true
#fsGroup: 1000
containerSecurityContext:
readOnlyRootFilesystem: true
privileged: false
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
ingress:
enabled: true
ingressClassName: openshift-default
annotations:
kubernetes.io/ingress.class: openshift-default
kubernetes.io/tls-acme: "true"
cert-manager.io/cluster-issuer: "letsencrypt-dns01-cloudflare"
labels: {}
hosts:
- host: mailhog.apilab.us
paths:
- path: "/"
pathType: Prefix
tls:
- secretName: mailhog-tls
hosts:
- mailhog.apilab.us
auth:
enabled: false
existingSecret: ""
fileName: auth.txt
fileContents:
# JSON file defining outgoing SMTP servers
outgoingSMTP:
enabled: false
existingSecret: ""
fileName: outgoing-smtp.json
fileContents:
{}
# See https://github.com/mailhog/MailHog/blob/master/docs/CONFIG.md#outgoing-smtp-configuration
# Only name, host and port are required.
#
# server_name1:
# name: "server_name1"
# host: "mail.example.com"
# port: "25" # NOTE: go requires this port number to be a string... otherwise the container won't start
# email: ""
# username: ""
# password: ""
# mechanism: "PLAIN|CRAM-MD5"
# server_name2:
# name: "server_name2"
# host: "mail2.example.com"
# port: "587" # NOTE: go requires this port number to be a string... otherwise the container won't start
podReplicas: 1
podAnnotations: {}
podLabels: {}
extraEnv: []
# ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes
livenessProbe:
initialDelaySeconds: 10
timeoutSeconds: 1
readinessProbe: {}
resources:
{}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
affinity: {}
nodeSelector: {}
tolerations: []
priorityClassName: