Skip to content

Commit 45f86cb

Browse files
doc: add clarification about current state of OLMv1 at upstream (#1502)
1 parent 53f15b5 commit 45f86cb

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/index.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,3 +37,12 @@ For more details on the evolution of OLM and the roadmap for v1, explore the fol
3737

3838
- [Multi-Tenancy Challenges, Lessons Learned, and Design Shifts](project/olmv1_design_decisions.md)
3939
- [OLM v1 Roadmap](project/olmv1_roadmap.md)
40+
41+
## Can I Migrate from OLMv0 to OLMv1?
42+
43+
There is currently no concrete migration strategy due to the [conceptual differences between OLMv0 and OLMv1](project/olmv1_design_decisions.md).
44+
OLMv1, as of writing, supports a subset of the existing content supported by OLMv0.
45+
For more information regarding the current limitations of OLMv1, see [limitations](project/olmv1_limitations.md).
46+
47+
If your current usage of OLMv0 is compatible with the limitations and expectations of OLMv1, you may be able to manually
48+
transition to using OLMv1 following the standard workflows we have documented.

0 commit comments

Comments
 (0)