forked from openfaas/faas-netes
-
Notifications
You must be signed in to change notification settings - Fork 0
/
values-pro.yaml
46 lines (37 loc) · 1.4 KB
/
values-pro.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
# Suggested additional overrides for OpenFaaS Pro users,
# in addition to (not instead of) values.yaml
# Initial configuration to set Pro configurations on
openfaasPro: true
# The operator mode supports the Function CustomResource
# which enables tooling like ArgoCD / Flux v2
operator:
create: true
# Do not turn off, enables authentication on all core components
generateBasicAuth: true
# Follow docs at: https://docs.openfaas.com/openfaas-pro/dashboard/
# for setting up the new dashboard
dashboard:
publicURL: https://dashboard.example.com
enabled: false
# https://docs.openfaas.com/architecture/autoscaling/
# The autoscaler is not enabled by default, but should be enabled here
autoscaler:
enabled: true
# A cluster role is required for OpenFaaS Pro due to:
# 1) Autoscaling and metrics for functions - CPU / RAM
# 2) Multiple namespace support
# https://docs.openfaas.com/reference/namespaces/
clusterRole: true
# HPA CPU? 3 <=> 6
# If you have purchased licenses for 6 gateway replicas for this environment
# you can create a HPA rule to scale on CPU, but you must not scale beyond
# what's been purchased.
gateway:
replicas: 3
# replicas x maxInflight = max concurrent messages processed.
# 75 concurrent requests will be processed, 25 per queueWorker
queueWorker:
replicas: 3
maxInflight: 25
# For timeouts longer than 60 seconds see:
# https://docs.openfaas.com/tutorials/expanded-timeouts/