-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathvalues.yaml
110 lines (102 loc) · 2.64 KB
/
values.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
vui:
#
# Global
#
global:
veleroNamespace: velero
# kubernetesClusterDomain: my-cluster
# agentMode: false
clusterName: velero
#
# API Config
#
apiConfig:
# To generate a fixed secure random secret key use the command: openssl rand -hex 32
# securityTokenKey:
#
existingSecret: vui-credentials
# debugLevel: debug
veleroCliVersion: v1.14.1
# apiTokenExpirationMin: "30"
# apiTokenRefreshExpirationDays: "7"
storage:
enabled: false
storageClassName: <your-storage-class-name>
#
# You can use nodeport or ingress according to your needs
#
#
# Nodeport
#
uiNp:
enabled: false
ip: "10.10.0.100" # any ip address of your cluster
apiPort: "30001"
uiPort: "30002"
#
# Ingress
#
uiIngress:
enabled: true
ingressClassName: nginx
metadata:
annotations:
cert-manager.io/cluster-issuer: "letsencrypt"
external-dns.alpha.kubernetes.io/target: "home.terence.cloud"
# nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
# nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
# nginx.ingress.kubernetes.io/server-snippets: |
# location /ws {
# proxy_http_version 1.1;
# proxy_set_header Upgrade $http_upgrade;
# proxy_set_header Connection "upgrade";
# }
spec:
tls:
- hosts:
- velero.terence.cloud
secretName: velero-ui-tls
#
# Watchdog Cron
#
report:
schedule: 0 8 * * *
#
# Watchdog Daemon
#
watchdogConfig:
# config
apiEndpointPort: "8001"
k8SInclusterMode: "True"
k8sVeleroNamespace: "velero"
processClusterName: homelab
# processCycleSec: 300
# expiresDaysWarning: 29
notificationSkipCompleted: "False"
# notificationSkipInProgress: "True"
# notificationSkipRemoved: "True"
# notificationSkipDeleting: "True"
# email
emailEnable: "False"
emailAccount: <your-email>
emailPassword: <your-password>
emailRecipients: <email-recipents-comma-saparted>
emailSmtpPort: <smtp-port>
emailSmtpServer: <smtp-server>
# slack
slackEnable: "False"
slackChannel: <channel-id>
slackToken: <token>
# TODO: telegram
telegramEnable: "False"
telegramChatId: "<telegram-chat-id>"
telegramToken: "<telegram-token>"
#
# uiConfig
# you can enable an experimental function to add a second cluster to the login screen
#
# uiConfig:
# experimental: true
# exNextPublicVeleroApiName2: "your-cluster-name-2"
# exNextPublicVeleroApiUrl2: "https://your-url-api-2/api"
# exNextPublicVeleroApiWs2: "wss://your-url-api-2"