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
Copy file name to clipboardExpand all lines: braintrust/README.md
+16-22Lines changed: 16 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Prerequisites
4
4
5
-
This helm chart requires a Kubernetes secret named `braintrust-secrets` to exist in the namespace where the chart is installed. Azure users can optionally use the Azure Key Vault CSI driver to automatically sync secrets from Azure Key Vault into Kubernetes (see below for details).
5
+
This helm chart requires a Kubernetes secret named `braintrust-secrets` to exist in the namespace where the chart is installed. Azure users will automatically sync secrets from Azure Key Vault into Kubernetes (see below for details). AWS and Google users will need to manually create and manage the `braintrust-secrets` Kubernetes secret.
6
6
7
7
## Required Secrets
8
8
@@ -19,32 +19,30 @@ The `braintrust-secrets` secret must contain the following keys:
19
19
|`GCS_ACCESS_KEY_ID`| Google HMAC Access ID string | Valid S3 API Key Id (only required if `cloud` is `google`) |
20
20
|`GCS_SECRET_ACCESS_KEY`| Google HMAC Secret string | Valid S3 Secret string (only required if `cloud` is `google`) |
21
21
22
-
## Azure Key Vault CSI Integration (Optional)
22
+
## Azure Key Vault Driver Integration
23
23
24
-
If you're using Azure, you can optionally use the Azure Key Vault CSI driver to automatically sync secrets from Azure Key Vault into Kubernetes. This eliminates the need to manually create and manage the `braintrust-secrets` Kubernetes secret.
24
+
If you're using Azure, the Azure Key Vault CSI driver is default enabled and will automatically sync secrets from Azure Key Vault into Kubernetes. This eliminates the need to manually create and manage the `braintrust-secrets` Kubernetes secret.
25
25
26
26
To enable this feature:
27
27
28
-
1. Set `azureKeyVaultCSI.enabled: true` in your values.yaml
29
-
2. Configure your Key Vault details:
28
+
1. Configure your Key Vault details:
30
29
31
30
```yaml
32
-
azureKeyVaultCSI:
33
-
enabled: true
34
-
name: "your-keyvault-name"
35
-
userAssignedIdentityID: "your-identity-id"
36
-
clientID: "your-client-id"
31
+
azure:
32
+
keyVaultName: "your-keyvault-name"
33
+
keyVaultCSIclientID: "your-client-id"# This should come from the terraform module
37
34
tenantId: "your-tenant-id"
38
35
```
39
36
40
-
3. Optionally map your Key Vault secret names to the required Kubernetes secret keys. This is only required if you aren't using our terraform module. The defaults assume you are using the Braintrust terraform module to deploy the base infrastructure.
37
+
2. Optionally map your Key Vault secret names to the required Kubernetes secret keys. This is only required if you aren't using our terraform module. The defaults assume you are using the Braintrust terraform module to deploy the base infrastructure.
- Each brainstore pod gets its own dedicated node with full access to local SSDs
93
91
94
-
**Supported machine families:** c4, c4d,
92
+
**Supported machine families:** c4, c4d
95
93
96
94
### GKE Standard Mode
97
95
@@ -102,7 +100,7 @@ For Standard mode clusters, create node pools with local SSDs, then deploy:
102
100
cloud: "google"
103
101
104
102
google:
105
-
mode: "standard"
103
+
mode: "standard"
106
104
107
105
brainstore:
108
106
reader:
@@ -150,10 +148,6 @@ For Standard mode clusters, create node pools with local SSDs, then deploy:
150
148
- Local SSDs are automatically available via emptyDir volumes
151
149
- Pod anti-affinity ensures readers and writers don't share nodes (each pod gets dedicated node access)
152
150
153
-
## Notes
154
-
155
-
- The `AZURE_STORAGE_CONNECTION_STRING` may or may not contain an AccountKey or SAS token depending on the storage account configuration. If a key or token is not provided, workload identity will be used.
156
-
- When using Azure Key Vault CSI, ensure your AKS cluster has the CSI driver installed and the managed identity has the correct permissions in Key Vault.
0 commit comments