Skip to content

Commit 8296cb6

Browse files
authored
docs: document ENABLE_INLINE_MILVUS limitations in README (#280)
[RHOAIENG-3916](https://issues.redhat.com/browse/RHOAIENG-3916) ### Description Companion to opendatahub-io/ogx-distribution#318. Documents that `inline::milvus` (enabled via `ENABLE_INLINE_MILVUS`) is only supported in single-worker, single-replica deployments. The operator does not manage or validate this env var. ### How Has This Been Tested? ```bash make test ``` ### Test Impact None. Documentation only. Approved-by: VaishnaviHire Approved-by: derekhiggins
1 parent 2d2ca4e commit 8296cb6

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,10 @@ spec:
9494
```
9595
3. Verify the server pod is running in the user defined namespace.
9696

97+
### Local Vector Storage (inline::milvus)
98+
99+
To enable the `inline::milvus` local vector storage provider, set `ENABLE_INLINE_MILVUS` in `spec.server.containerSpec.env`. This is only supported in single-worker, single-replica deployments. Milvus-Lite uses SQLite internally and does not support concurrent access from multiple processes.
100+
97101
### Using a ConfigMap for config.yaml configuration
98102

99103
A ConfigMap can be used to store config.yaml configuration for each LlamaStackDistribution.

0 commit comments

Comments
 (0)