-
Notifications
You must be signed in to change notification settings - Fork 16
/
Copy pathvalues.yaml
115 lines (99 loc) · 3.26 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
111
112
113
114
115
## Default values for Epinio Helm Chart.
## This is a YAML-formatted file.
## Declare variables to be passed into your templates.
# The email address you are planning to use for getting notifications about your certificates.
email: "epinio@suse.com"
# The URL of the container registry from where to pull container images
# for the various created Pods. Don't confuse this registry with the "Epinio
# registry" which is the one where Epinio stores the application images.
registryURL: ""
image:
epinio:
repository: ghcr.io/epinio/epinio-server
tag: ""
bash:
repository: library/bash
tag: 5.1.4
awscli:
repository: amazon/aws-cli
tag: 2.0.52
kubectl:
repository: lachlanevenson/k8s-kubectl
tag: v1.22.2
server:
# Domain which serves the Rancher UI (to access the API)
accessControlAllowOrigin: ""
# increase this value to increase all timeouts by the same factor
timeoutMultiplier: 1
# Change this to a random string. Used for session cookies by the API server.
sessionKey: "12345"
# Increase this value to instruct the API server to produce more debug output
traceLevel: 0
# The ingressClassName is used to select the ingress controller for apps. If empty no class will be added to their ingresseses.
ingressClassName: ""
ingress:
# The ingressClassName is used to select the ingress controller for the server. If empty no class will be added to the ingresses.
ingressClassName: ""
certManagerNamespace: cert-manager
# Connection details for the S3 storage
s3:
endpoint: s3.amazonaws.com
bucket: ""
region: ""
accessKeyID: ""
secretAccessKey: ""
useSSL: true
# Set it to an existing secret if S3 is using a self signed cert
certificateSecret: ""
api:
# Default user username
username: admin
# Default user password
password: password
# Minio subchart values
minio:
enabled: true
# hardcode this, to avoid problems with release name
fullnameOverride: minio
existingSecret: minio-creds
tls:
enabled: true
certSecret: minio-tls
publicCrt: tls.crt
privateKey: tls.key
persistence:
size: 2Gi
drivesPerNode: 4
replicas: 1
resources:
requests:
memory: 1Gi
makeUserJob:
podAnnotations:
linkerd.io/inject: disabled
kubed:
enabled: true
fullnameOverride: kubed
enableAnalytics: false
containerregistry:
enabled: true
image: registry:2.7.1
imagePullPolicy: IfNotPresent
# We create a service with type `NodePort` only in
# local deployment as Kubelet cannot access the
# secured registry because there is no way to add
# registry CA to kubelet.
createNodePort: true
# The ingressClassName is used to select the ingress controller. If empty no class will be added to the ingresses.
ingressClassName: ""
global:
# The domain that will be used to access the epinio API server and the registry
domain: ""
# Connection details for the container registry.
registryURL: "" # Skip if containerregistry.enabled is true
registryUsername: "admin"
registryPassword: "changeme"
registryNamespace: "apps" # Used in registry path when pushing -> "external.tld/apps/APPNAME"
# The name of the cluster issuer to use.
# Epinio creates three options: 'epinio-ca', 'letsencrypt-production', and 'selfsigned-issuer'.
tlsIssuer: "epinio-ca"