/
wc-config.yaml
319 lines (274 loc) · 8.89 KB
/
wc-config.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
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
# This configuration applies to the workload cluster.
# It will override settings set in "defaults/common-config.yaml".
global:
## The cluster name.
## Used in logs and metrics as to separate these from other clusters.
clusterName: ${CK8S_ENVIRONMENT_NAME}-wc
## If baseDomain for wc and sc are not the same, set the domain of the sc cluster.
scDomain: ""
scOpsDomain: ""
## User configuration.
user:
## This only controls if the namespaces should be created, user RBAC is always created.
createNamespaces: true
## List of user namespaces to create.
namespaces:
- set-me
- demo
## Any namespace listed in constraints are exempted from HNC managed namespaces
## This to override the Pod Security Admission level
## Example of constraint can be found here: helmfile/charts/gatekeeper/podsecuritypolicies/values.yaml
## The only extra label "psaLevel: <baseline/privileged>" is shown in the following example:
## <namespace>:
## psaLevel: <baseline/privileged>
## <service-name>:
## ...
constraints: {}
## List of users to create RBAC rules for.
adminUsers:
- set-me
- admin@example.com
## List of serviceAccounts to create RBAC rules for, used for dev situations.
serviceAccounts: []
## List of groups to create RBAC rules for.
adminGroups:
- set-me
## User controlled alertmanager configuration.
alertmanager:
enabled: true
resources:
requests:
cpu: 10m
memory: 50Mi
limits:
cpu: 50m
memory: 100Mi
tolerations: []
affinity: {}
topologySpreadConstraints: []
# image: quay.io/prometheus/alertmanager:vX.Y.Z
# Installs required cluster resources needed to install sealedSecrets
# Requires that gatekeeper.allowUserCRDs.enabled is enabled.
sealedSecrets:
enabled: false
# Installs required cluster resources needed to install mongodb
# Requires that gatekeeper.allowUserCRDs.enabled is enabled.
mongodb:
enabled: false
# Installs required cluster resources needed to install fluxv2
# Requires that gatekeeper.allowUserCRDs.enabled is enabled.
fluxv2:
enabled: false
# Installs required cluster resources needed to install kafka-operator
# Requires that gatekeeper.allowUserCRDs.enabled is enabled.
kafka:
enabled: false
falco:
## Falco alerting configuration.
alerts:
enabled: true
## supported: 'alertmanager', 'slack'.
type: alertmanager
priority: notice
hostPort: http://alertmanager-operated.alertmanager:9093
## Prometheus configuration.
## Prometheus collects metrics and pushes it to Thanos.
prometheus:
## Additional prometheus scrape config.
## ref: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config
additionalScrapeConfigs: []
velero:
storagePrefix: workload-cluster
## Excluded namespaces
excludedNamespaces:
- cert-manager
- falco
- fluentd
- hnc-system
- ingress-nginx
- kube-node-lease
- kube-public
- kube-system
- kured
- monitoring
- rook-ceph
- velero
- gatekeeper-system
## Extra excluded namespace, here we should add the namespaces that are more likely to change
excludedExtraNamespaces: []
## Hierarchical namespace controller configuration, enable in common-config.yaml
hnc:
## Included namespaces, empty string will include all
includedNamespacesRegex: ""
## Excluded namespaces
excludedNamespaces:
- alertmanager
- cert-manager
- falco
- fluentd
- fluentd-system
- hnc-system
- ingress-nginx
- kube-node-lease
- kube-public
- kube-system
- kured
- monitoring
- rook-ceph
- velero
- gatekeeper-system
- metallb-system
## Extra excluded namespace, here we should add the namespaces that are more likely to change
excludedExtraNamespaces: []
## Additional resources to enable opt-in propagation for.
## Objects that should be propagated must have one of the annotations listed here https://github.com/kubernetes-sigs/hierarchical-namespaces/blob/master/docs/user-guide/how-to.md#limit-the-propagation-of-an-object-to-descendant-namespaces
additionalAllowPropagateResources: []
## examples:
## - resource: secrets
## - resource: networkpolicies
## group: networking.k8s.io
## Annotations that will be stripped from propagated objects
unpropagatedAnnotations: []
## Annotations that will be propagated to subnamespaces (allows regex)
managedNamespaceAnnotations: []
## Labels that will be propagated to subnamespaces (allows regex)
## Labels in particular must also be configured in the HierarchyConfiguration object to be propagated
managedNamespaceLabels:
- pod-security.kubernetes.io/enforce
- pod-security.kubernetes.io/audit
- pod-security.kubernetes.io/warn
## Manager deployment configuration
manager:
resources:
requests:
cpu: 100m
memory: 150Mi
limits:
cpu: 100m
memory: 300Mi
nodeSelector: {}
tolerations: []
affinity: {}
## Enables HA mode for hnc webhooks
ha: true
## This feature is only available in Kubernetes v1.28+ (https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#matching-requests-matchconditions)
## It will be changed to true by default when v1.27 is closer to EOL.
webhookMatchConditions: false
## Webhook deployment configuration, only used if hnc.ha is true
webhook:
replicaCount: 3
resources:
requests:
cpu: 100m
memory: 150Mi
limits:
cpu: 100m
memory: 300Mi
topologySpreadConstraints:
- labelSelector:
matchLabels:
app.kubernetes.io/component: hnc-webhook
maxSkew: 1
topologyKey: kubernetes.io/hostname
whenUnsatisfiable: DoNotSchedule
nodeSelector: {}
tolerations: []
affinity: {}
## Service monitor configuration
serviceMonitor:
relabelings: []
## certmanager:
## when using cert-manager with HTTP01 challenge and a custom image registry the below parameter should be added in the extraArgs
## !! this works only with public repositories !! see https://github.com/jetstack/cert-manager/issues/2429
## update the image tag based on the version used in the helm chart
## - --acme-http01-solver-image=<harbor_server_name>/<proxy_project_name>/jetstack/cert-manager-acmesolver:v1.4.0
## extraArgs: []
## Configuration for fluentd.
## Fluentd ships logs to OpenSearch using the endpoint 'opensearch.subdomain' set in common-config.yaml.
## Consists of two different deployments, one for running on master nodes
## and and one for running on "user nodes".
fluentd:
enabled: true
## Only run on master nodes.
forwarder:
buffer:
chunkLimitSize: 8MB
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: node-role.kubernetes.io/control-plane
operator: Exists
## Extra fluentd config to mount.
extraConfigMaps: {}
## User controllable fluentd deployment.
## These pods collect logs from nodes where the user can run pods.
## Users can specify additional plugins and config in the respective configmaps:
## 'fluentd-extra-plugins', and 'fluentd-extra-config'.
user:
resources:
requests:
cpu: 100m
memory: 300Mi
limits:
cpu: 500m
memory: 1000Mi
tolerations: []
nodeSelector: {}
affinity: {}
externalTrafficPolicy:
# Whitelisting requires externalTrafficPolicy.local to be true
# local: true
# Comma separated list of CIDRs, e.g. 172.16.0.0/24,172.24.0.0/24
whitelistRange:
# global: 0.0.0.0/0
kubeapiMetrics: false
wcProbeIngress:
enabled: true
prometheusBlackboxExporter:
targets:
gatekeeper: true
falco: true
sc: true
ingressNginx:
subDomain: ingress-nginx
# Network policies for workload cluster
networkPolicies:
global:
wcApiserver:
# usually private ip of control-plane nodes
ips:
- set-me
port: 6443
wcNodes:
# ip of all nodes in the cluster for internal communication
ips:
- set-me
monitoring:
enabled: true
fluentd:
enabled: true
ingressNginx:
ingressOverride:
ips: set-me-if-enabled
certManager:
namespaces: []
alertmanager:
enabled: true
## Open Policy Agent Gatekeeper configuration
gatekeeper:
allowUserCRDs:
enabled: false
enforcement: deny
# The name of the user specified in /etc/kubernetes/admin.conf kubeconfig file of the control plane nodes
# Necessary if Kubespray is used for managing the k8s cluster.
adminConfUser: kubernetes-admin
extraCRDs: []
# Sealed secrets and MongoDB CRDs can be enabled via user.sealedsecrets/mongodb
# - names:
# - sealedsecrets.bitnami.com
# group: "bitnami.com"
extraServiceAccounts: []
# - namespace: "gatekeeper-system"
# name: "gatekeeper-admin-upgrade-crds"