This repository has been archived by the owner on May 6, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 385
/
values.yaml
118 lines (118 loc) · 4.69 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
116
117
118
# Default values for Service Catalog
# service-catalog image to use
image: quay.io/kubernetes-service-catalog/service-catalog:v0.3.0
# imagePullSecrets pre-existing secrets to use to pull images from a private registry
imagePullSecrets: []
# imagePullPolicy for the service-catalog; valid values are "IfNotPresent",
# "Never", and "Always"
imagePullPolicy: Always
## If true, create & use RBAC resources
##
rbacEnable: true
rbacApiVersion: rbac.authorization.k8s.io/v1
webhook:
# updateStrategy for service-catalog; value values are "RollingUpdate" and "Recreate"
updateStrategy: RollingUpdate
minReadySeconds: 1
# annotations is a collection of annotations to add to the webhook pods.
annotations: {}
# nodeSelector to apply to the webhook pods
nodeSelector:
# healthcheck configures the readiness and liveliness probes for the webhook pod.
healthcheck:
enabled: true
# Attributes of the webhook's service resource
service:
# Type of service; valid values are "LoadBalancer", "NodePort" or "ClusterIP"
# NodePort is useful if deploying on bare metal or hacking locally on
# minikube
port: 443
type: NodePort
# Further configuration for services of type NodePort
nodePort:
# Available port in allowable range (e.g. 30000 - 32767 on minikube)
# The TLS-enabled endpoint will be exposed here
securePort: 31443
# Log level; valid values are in the range 0 - 10
verbosity: 10
serviceAccount: service-catalog-webhook
# Webhook resource requests and limits
# Ref: http://kubernetes.io/docs/user-guide/compute-resources/
resources:
requests:
cpu: 100m
memory: 20Mi
limits:
cpu: 100m
memory: 30Mi
controllerManager:
replicas: 1
# updateStrategy for service-catalog; value values are "RollingUpdate" and "Recreate"
updateStrategy: RollingUpdate
minReadySeconds: 1
# annotations is a collection of annotations to add to the controllerManager pod.
annotations: {}
# nodeSelector to apply to the controllerManager pods
nodeSelector:
# healthcheck configures the readiness and liveliness probes for the controllerManager pod.
healthcheck:
enabled: true
# Log level; valid values are in the range 0 - 10
verbosity: 10
# Resync interval; format is a duration (`20m`, `1h`, etc)
resyncInterval: 5m
# Broker relist interval; format is a duration (`20m`, `1h`, etc)
brokerRelistInterval: 24h
# Whether or not the controller supports a --broker-relist-interval flag. If this is
# set to true, brokerRelistInterval will be used as the value for that flag
brokerRelistIntervalActivated: true
# The maximum amount of time to back-off while polling an OSB API operation; format is a duration (`20m`, `1h`, etc)
operationPollingMaximumBackoffDuration: 20m
# The maximum amount of timeout to any request to the broker; format is a duration (`60s`, `3m`, etc)
osbApiRequestTimeout: 60s
# enables profiling via web interface host:port/debug/pprof/
profiling:
# Disable profiling via web interface host:port/debug/pprof/
disabled: false
# Enables lock contention profiling, if profiling is enabled.
contentionProfiling: false
leaderElection:
# Whether the controller has leader election enabled.
activated: false
serviceAccount: service-catalog-controller-manager
# Whether the controller will expose metrics on /metrics
enablePrometheusScrape: false
# Controller Manager resource requests and limits
# Ref: http://kubernetes.io/docs/user-guide/compute-resources/
resources:
requests:
cpu: 100m
memory: 20Mi
limits:
cpu: 100m
memory: 30Mi
# Attributes of the controller's service resource
service:
# Type of service; valid values are "LoadBalancer", "NodePort" and "ClusterIP"
# NodePort is useful if deploying on bare metal or hacking locally on
# minikube
type: ClusterIP
# Further configuration for services of type NodePort
nodePort:
# Available port in allowable range (e.g. 30000 - 32767 on minikube)
# The TLS-enabled endpoint will be exposed here
securePort: 30444
# Whether the OriginatingIdentity feature should be enabled
originatingIdentityEnabled: true
# Whether the AsyncBindingOperations alpha feature should be enabled
asyncBindingOperationsEnabled: false
# Whether the NamespacedServiceBroker feature should be disabled
namespacedServiceBrokerDisabled: false
# Whether the ServicePlanDefaults alpha feature should be enabled
servicePlanDefaultsEnabled: false
# Whether the CascadingDeletion alpha feature should be enabled
cascadingDeletionEnabled: false
## Security context give the opportunity to run container as nonroot by setting a securityContext
## by example :
## securityContext: { runAsUser: 1001 }
securityContext: {}