forked from feast-dev/feast
-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathvalues.yaml
More file actions
205 lines (199 loc) · 7.72 KB
/
values.yaml
File metadata and controls
205 lines (199 loc) · 7.72 KB
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
# Feast deployment installs the following components:
# - Feast Core
# - Feast Serving Online
# - Feast Serving Batch
#
# The configuration for different components can be referenced from:
# - charts/feast-core/values.yaml
# - charts/feast-serving/values.yaml
#
# Note that "feast-serving-online" and "feast-serving-batch" are
# aliases to "feast-serving" chart since in typical scenario two instances
# of Feast Serving: online and batch will be deployed. Both described
# using the same chart "feast-serving".
#
# The following are default values for typical Feast deployment, but not
# for production setting. Refer to "values-production.yaml" for recommended
# values in production environment.
#
# Note that the import job by default uses DirectRunner
# https://beam.apache.org/documentation/runners/direct/
# in this configuration since it allows Feast to run in more environments
# (unlike DataflowRunner which requires Google Cloud services).
#
# A secret containing Google Cloud service account JSON key is required
# in this configuration.
# https://cloud.google.com/iam/docs/creating-managing-service-accounts
#
# The Google Cloud service account must have the following roles:
# - bigquery.dataEditor
# - bigquery.jobUser
#
# Assuming a service account JSON key file has been downloaded to
# (please name the file key.json):
# /home/user/key.json
#
# Run the following command to create the secret in your Kubernetes cluster:
#
# kubectl create secret generic feast-gcp-service-account \
# --from-file=/home/user/key.json
#
# ============================================================
# Feast Core
# ============================================================
feast-core:
# enabled specifies whether to install Feast Core component.
#
# Normally, this is set to "false" when Feast users need access to low latency
# Feast Serving, by deploying multiple instances of Feast Serving closest
# to the client. These instances of Feast Serving however can still use
# the same shared Feast Core.
enabled: true
# jvmOptions are options that will be passed to the Java Virtual Machine (JVM)
# running Feast Core.
#
# For example, it is good practice to set min and max heap size in JVM.
# https://stackoverflow.com/questions/6902135/side-effect-for-increasing-maxpermsize-and-max-heap-size
jvmOptions:
- -Xms1024m
- -Xmx1024m
# resources that should be allocated to Feast Core.
resources:
requests:
cpu: 1000m
memory: 1024Mi
limits:
memory: 2048Mi
# gcpServiceAccount is the Google service account that Feast Core will use.
gcpServiceAccount:
# useExistingSecret specifies Feast to use an existing secret containing
# Google Cloud service account JSON key file.
#
# This is the only supported option for now to use a service account JSON.
# Feast admin is expected to create this secret before deploying Feast.
useExistingSecret: true
existingSecret:
# name is the secret name of the existing secret for the service account.
name: feast-gcp-service-account
# key is the secret key of the existing secret for the service account.
# key is normally derived from the file name of the JSON key file.
key: key.json
# ============================================================
# Feast Serving Online
# ============================================================
feast-serving-online:
# enabled specifies whether to install Feast Serving Online component.
enabled: true
# redis.enabled specifies whether Redis should be installed as part of Feast Serving.
#
# If enabled is set to "false", Feast admin has to ensure there is an
# existing Redis running outside Feast, that Feast Serving can connect to.
redis:
enabled: true
# jvmOptions are options that will be passed to the Feast Serving JVM.
jvmOptions:
- -Xms1024m
- -Xmx1024m
# resources that should be allocated to Feast Serving.
resources:
requests:
cpu: 500m
memory: 1024Mi
limits:
memory: 2048Mi
# store.yaml is the configuration for Feast Store.
#
# Refer to this link for more description:
# https://github.com/gojek/feast/blob/79eb4ab5fa3d37102c1dca9968162a98690526ba/protos/feast/core/Store.proto
store.yaml:
name: redis
type: REDIS
redis_config:
# If redis.enabled is set to false, Feast admin should uncomment and
# set the host value to an "existing" Redis instance Feast will use as
# online Store.
#
# Else, if redis.enabled is set to true, no additional configuration is
# required.
#
# host: redis-host
port: 6379
subscriptions:
- name: "*"
project: "*"
version: "*"
# ============================================================
# Feast Serving Batch
# ============================================================
feast-serving-batch:
# enabled specifies whether to install Feast Serving Batch component.
enabled: true
# redis.enabled specifies whether Redis should be installed as part of Feast Serving.
#
# This is usually set to "false" for Feast Serving Batch because the default
# store is BigQuery.
redis:
enabled: false
# jvmOptions are options that will be passed to the Feast Serving JVM.
jvmOptions:
- -Xms1024m
- -Xmx1024m
# resources that should be allocated to Feast Serving.
resources:
requests:
cpu: 500m
memory: 1024Mi
limits:
memory: 2048Mi
# gcpServiceAccount is the service account that Feast Serving will use.
gcpServiceAccount:
# useExistingSecret specifies Feast to use an existing secret containing
# Google Cloud service account JSON key file.
#
# This is the only supported option for now to use a service account JSON.
# Feast admin is expected to create this secret before deploying Feast.
useExistingSecret: true
existingSecret:
# name is the secret name of the existing secret for the service account.
name: feast-gcp-service-account
# key is the secret key of the existing secret for the service account.
# key is normally derived from the file name of the JSON key file.
key: key.json
# application.yaml is the main configuration for Feast Serving application.
#
# Feast Core is a Spring Boot app which uses this yaml configuration file.
# Refer to https://github.com/gojek/feast/blob/79eb4ab5fa3d37102c1dca9968162a98690526ba/serving/src/main/resources/application.yml
# for a complete list and description of the configuration.
application.yaml:
feast:
jobs:
# staging-location specifies the URI to store intermediate files for
# batch serving (required if using BigQuery as Store).
#
# Please set the value to an "existing" Google Cloud Storage URI that
# Feast serving has write access to.
staging-location: gs://bucket/path
# Type of store to store job metadata.
#
# This default configuration assumes that Feast Serving Online is
# enabled as well. So Feast Serving Batch will share the same
# Redis instance to store job statuses.
store-type: REDIS
# store.yaml is the configuration for Feast Store.
#
# Refer to this link for more description:
# https://github.com/gojek/feast/blob/79eb4ab5fa3d37102c1dca9968162a98690526ba/protos/feast/core/Store.proto
store.yaml:
name: bigquery
type: BIGQUERY
bigquery_config:
# project_id specifies the Google Cloud Project. Please set this to the
# project id you are using BigQuery in.
project_id: PROJECT_ID
# dataset_id specifies an "existing" BigQuery dataset Feast Serving Batch
# will use. Please ensure this dataset is created beforehand.
dataset_id: DATASET_ID
subscriptions:
- name: "*"
project: "*"
version: "*"