Files
k3s/argocd/apps/mattermost/mattermnost.yaml
2025-11-27 09:05:37 +01:00

75 lines
2.1 KiB
YAML

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: mattermost
spec:
project: default
source:
repoURL: 'https://helm.mattermost.com'
targetRevision: 6.*.*
chart: mattermost-team-edition
helm:
valuesObject:
# Persistence für Mattermost Daten
persistence:
data:
enabled: true
size: 10Gi
storageClass: "longhorn"
accessMode: ReadWriteOnce
plugins:
enabled: true
size: 1Gi
storageClass: "longhorn"
accessMode: ReadWriteOnce
# MySQL SubChart AKTIVIERT (für die Datenbank)
mysql:
enabled: true
mysqlRootPassword: "mmROOT12345"
mysqlUser: "mmdbuser"
mysqlPassword: "mmdbpwd"
mysqlDatabase: mattermost
testFramework:
enabled: false
persistence:
enabled: true
storageClass: "longhorn"
accessMode: ReadWriteOnce
size: 10Gi
# TRICK: externalDB aktivieren, damit das Chart NICHT das
# fehlerhafte MM_CONFIG Secret generiert!
# Wir zeigen auf die interne MySQL mit korrektem DSN Format
externalDB:
enabled: true
externalDriverType: "mysql"
externalConnectionString: "mmdbuser:mmdbpwd@tcp(mattermost-mysql:3306)/mattermost?charset=utf8mb4,utf8&readTimeout=30s&writeTimeout=30s"
# Ingress Konfiguration
ingress:
enabled: true
hosts:
- mattermost.innovation-hub-niedersachsen.de
tls:
- hosts:
- mattermost.innovation-hub-niedersachsen.de
secretName: mattermost-tls
annotations:
kubernetes.io/ingress.class: traefik
cert-manager.io/cluster-issuer: lets-encrypt-staging
destination:
server: 'https://kubernetes.default.svc'
namespace: mattermost
syncPolicy:
managedNamespaceMetadata:
labels:
pod-security.kubernetes.io/enforce: "privileged"
automated:
selfHeal: true
prune: true
syncOptions:
- CreateNamespace=true