You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This Feast chart comes with a [values.yaml](values.yaml) that allows for configuration and customization of all sub-charts.
33
42
34
-
The feature server requires a base64-encoded `feature_store.yaml` to be provided:
43
+
The feature server requires a base64-encoded `feature_store.yaml`. You can either reference a pre-existing Kubernetes Secret or provide the value inline:
35
44
36
45
```yaml
37
46
feature-server:
47
+
# Option A: reference an existing Secret (recommended)
48
+
existingSecret: my-feast-config
49
+
# Option B: provide inline (stored in Helm release metadata)
> **Upgrading from the Java chart?** See the [feature-server migration guide](charts/feature-server/README.md#migration-from-java-chart) for details on removed gRPC and Java-specific values.
54
+
41
55
For more details, please see: https://docs.feast.dev/how-to-guides/running-feast-in-production
> **Note:** When using `--set`, the base64-encoded config is stored in Helm release metadata and is retrievable via `helm get values`. Use Option A or an external secrets operator (e.g. SealedSecrets, ExternalSecrets) for production deployments with sensitive credentials.
80
+
9
81
## Values
10
82
11
83
| Key | Type | Default | Description |
12
84
|-----|------|---------|-------------|
13
85
| envOverrides | object |`{}`| Extra environment variables to set |
14
-
| feature_store_yaml_base64 | string |`""`|[required] a base64 encoded version of feature_store.yaml |
86
+
| existingSecret | string |`""`| Name of an existing Secret containing key `feature_store_yaml_base64` with base64-encoded config |
87
+
| feature_store_yaml_base64 | string |`""`|[required] a base64 encoded version of feature_store.yaml (stored in a K8s Secret) |
0 commit comments