forked from zarf-dev/zarf
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathgitea-values.yaml
58 lines (52 loc) · 1.63 KB
/
gitea-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
persistence:
storageClass: "###ZARF_STORAGE_CLASS###"
claimName: "###ZARF_VAR_GIT_SERVER_EXISTING_PVC###"
size: "###ZARF_VAR_GIT_SERVER_PVC_SIZE###"
accessModes:
- "###ZARF_VAR_GIT_SERVER_PVC_ACCESS_MODE###"
create: ###ZARF_VAR_GIT_SERVER_CREATE_PVC###
replicaCount: ###ZARF_VAR_GIT_SERVER_REPLICA_COUNT###
gitea:
admin:
username: "###ZARF_GIT_PUSH###"
password: "###ZARF_GIT_AUTH_PUSH###"
email: "zarf@localhost"
config:
APP_NAME: "Zarf Gitops Service"
server:
DISABLE_SSH: true
OFFLINE_MODE: true
ROOT_URL: http://zarf-gitea-http.zarf.svc.cluster.local:3000
database:
DB_TYPE: sqlite3
# Note that the init script checks to see if the IP & port of the database service is accessible, so make sure you set those to something that resolves as successful (since sqlite uses files on disk setting the port & ip won't affect the running of gitea).
HOST: zarf-docker-registry.zarf.svc.cluster.local:5000
security:
INSTALL_LOCK: true
service:
DISABLE_REGISTRATION: ###ZARF_VAR_GIT_SERVER_DISABLE_REGISTRATION###
repository:
ENABLE_PUSH_CREATE_USER: true
FORCE_PRIVATE: true
session:
PROVIDER: memory
cache:
ADAPTER: memory
queue:
TYPE: level
resources:
requests:
cpu: "###ZARF_VAR_GIT_SERVER_CPU_REQ###"
memory: "###ZARF_VAR_GIT_SERVER_MEM_REQ###"
limits:
cpu: "###ZARF_VAR_GIT_SERVER_CPU_LIMIT###"
memory: "###ZARF_VAR_GIT_SERVER_MEM_LIMIT###"
image:
fullOverride: "###ZARF_CONST_GITEA_IMAGE###"
rootless: true
postgresql-ha:
enabled: false
redis-cluster:
enabled: false
strategy:
type: "Recreate"