This guide will explain what migrating a project from Renku 1.0 to 2.0 means, and walk you through how to migrate your project.
The project code repository will be migrated automatically, and will show up in your Renku 2.0 project under the Code repositories section.
Git LFS data, including Renku Datasets, are a part of your code repository, and will be available from inside your Renku 2.0 session via the git lfs command line tool.
Git LFS data will not be downloaded automatically upon session launch, so you must run git lfs pull inside your session.
<aside> <img src="/icons/warning_yellow.svg" alt="/icons/warning_yellow.svg" width="40px" />
Warning: Please note that Renku 2.0 takes a significantly different approach to data compared to Renku 1.0. Read more on our blog. Consider moving your data into an external storage system and connecting it to your project via a Data connector.
</aside>
Cloud storage migration isn’t available at the moment. Please reconfigure your cloud storage as a Renku 2.0 Data connector.
By default, the Renku 2.0 project will be created with a Session Launcher that uses the latest image created for the 1.0 project.
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
Info: The session image will not continue to update as you make additional commits. This functionality is coming to Renku 2.0 soon! For more info, check out our design doc: Define a custom environment from a repo
</aside>
If you have a pinned image, the pinned image will be used.
The default resource class used by your Renku 1.0 project session will be set as the default resource class in the Renku 2.0 session launcher.
You may continue to use Renku workflows in your session via the CLI.
<aside> <img src="/icons/warning_yellow.svg" alt="/icons/warning_yellow.svg" width="40px" />
Warning: Please note that Renku 2.0 takes a significant different approach to workflows compared to Renku 1.0. Read more on our blog.
</aside>