This release introduces copying projects. This feature makes it easy for course instructors to distribute course materials to students.
🌟 New Features
- UI: Introduce the ability to make a copy of a project, and to mark a project as a template intended for copying. (#3427).
Renku 0.62.1 fixes a bug that prevented users to launch sessions with user secrets in Renku 1.0.
🐞 Bug Fixes
- Data services: Correctly map user secrets in Renku 1.0 sessions to use the provided filename.
This release introduces session secrets, which make it possible to connect to protected resources, such as databases or external compute systems, from a Renku session in a standardized and shareable manner. Collaborating with secrets is easy too: configure a single session secret slot to ensure that the secret shows up the same way for everyone, and each person enters their own value.
In addition, we have also made it much easier to configure and use PolyBox and SwitchDrive data connectors.
For administrators: This release removes the Gitlab omnibus Helm chart that we created and used to have as a dependency of the Renku Helm chart. We have been discouraging anyone from using this chart in production and we specified this in our documentation as well.
If you are using the internal Gitlab Helm chart then ensure to migrate to a separate Gitlab deployment as specified in our documentation. before installing this or any subsequent Renku version. Gitlab publishes an official Helm chart and that is what should be used for deploying Gitlab with Helm.
🌟 New Features
- UI: Configure and save session secrets in Renku 2.0 projects and use them in sessions (#3413).
Improvements
- UI: Simplify the creation of PolyBox and SwitchDrive data connectors (#3396).
- UI: Simplify the project and group creation interactions in Renku 2.0 to a simple modal (#3399).
- UI: Introduce a refreshed design for the dashboard, user, and group pages in Renku 2.0 (#3407, #3428).
New Features
- Data services: Support saving session secrets in Renku 2.0 projects and mounting them in sessions.
Improvements
- Infrastructure Components:
redishas been upgraded from version7.0.7to7.4.1 - Helm chart: remove the custom-made Gitlab Omnibus Helm chart from Renku dependencies
- Search services: Add support for sentry
Bug Fixes
- Search services: Don't return results without linked namespaces
Renku 0.61.2 fixes a bug that prevented users from resuming Renku V2 sessions after they have been hibernated because they were idle.
🐞 Bug Fixes
- Sessions: Correctly resume hibernated sessions.
Renku 0.61.1 introduces a few bug fixes for the previous release.
🐞 Bug Fixes
- Sessions: Correctly launch sessions that request dedicated resources classes
Bug Fixes
- Amalthea: Add resource requests for the authentication proxy containers
- Amalthea: Add support for setting priority classes for sessions
- Data services: Use the working directory to mount cloud storage if the mount path is relative
- Data services: Use HTTPS in the redirect URL for the authentication proxy
- Data services: Use GPU resource limits when GPUs are requested
- Helm chart: Do not set the default storage class to empty string if it is not set in the values file
- Helm chart: Restart the data services and notebooks pods when the mounted secret changes
Renku 0.61.0 introduces a new version of Amalthea that supports running sessions with Docker images that do not contain Jupyter server.
NOTES to administrators:
- This upgrade introduces a brand new CRD for sessions. All services that support sessions for Renku v2 will switch to this new CRD. Renku v1 sessions remain unchanged. Therefore any old sessions for Renku v2 will not be visible to users after this upgrade. The sessions themselves will not be immediately deleted and as long as users have saved links to their old sessions they should be able to access their sessions and save data. However we recommend that administrators notify users of the change and allow for enough time so that existing Renku v2 sessions can be saved and cleaned up, rather than asking users to save the url to their sessions. In addition to users not being able to see old Renku v2 sessions, they will also not be able to pause, resume or delete old Renku v2 sessions. Therefore it's best if most sessions are properly saved and cleaned up before this update is rolled out. In order to support the new CRD we have also created a new operator that will manage the new amaltheasession resources.
- The network policies for Renku have been consolidated and revamped. The most notable change here is the removal of the egress policy that prevented egress to internal IP addresses from sessions. Now we disallow all ingress in the Renku release namespace by default and explicitly grant permissions to any pods that need to access other pods inside the Renku release namespace. Two properties relevant to this have been added to the Helm chart values file that allows administrators to grant access to all Renku services from a specific namespace or to do the same for specific pods within the Renku namespace. These are not needed for Renku to function and the default network policies should be sufficient, they have been added so that administrators can allow ingress for other services that may not come with the Renku Helm chart such as logging or monitoring. This change will result in the removal of some network policies and the creation of several new policies.
✨ Improvements
- UI: Enable the use of custom images that don’t contain Jupyter, streamlining the image-building process and allowing for the use of “off-the-shelf” images (#3341).
- Sessions: Enable running session images that do not contain Jupyter in them.
Improvements
- Data services: Add support for OAuth storage providers
- Data services: Move notebooks code to data services
- Helm chart: Consolidate and revamp network policies
- Data services: Add support for project documentation
- Data services: Add support for cloning projects
Bug Fixes
- Gateway: Pass on session cookie to data services for anonymous session authentication
- Data services: Correct pagination for namespaces
- Data services: Add creation date and created_by for namespaces
- Data services: Pin RClone version in data services image
- Data services: Properly handle multi-architecture docker images when getting working directory
- Data services: Make environment working directory and mount directory optional
- Amalthea: Add readiness and health checks to sessions.
- Amalthea: Do not authenticate the authentication proxy health check
- Amalthea: Do not mount the Kubernetes service account in sessions
- Amalthea: Do not add Kubernetes specific environment variables in sessions
- renku-gateway 1.3.1
- renku-ui 3.42.0
- renku-data-services 0.26.0
- renku-data-services 0.27.0
- amalthea 0.13.0
- amalthea 0.14.0
- amalthea 0.14.1
- amalthea 0.14.2
- amalthea 0.14.3
- amalthea 0.14.4
Renku 0.60.0 squashes an issue that has been tripping up many users when connecting their GitHub account, as well as various UX polish and bug fixes.
NOTE to administrators: Upgrading the csi-rclone component will unmount all cloud storage for all active or hibernated sessions. Therefore, we recommend notifying your users ahead of time when you deploy this version of Renku and also if possible deploying the upgrade when there are fewer sessions that use cloud storage or just fewer sessions in general. Once the upgrade is complete users will be able to mount cloud storage as usual.
✨ Improvements
- UI: Allow for changing the role of members of groups, and hide membership edit buttons for users with insufficient permissions on project and group settings pages (#3374).
- UI: Improve UX for data connector side sheets and modals (#3368).
🐞 Bug Fixes
- UI & Data services: Direct users to complete the GitHub integration by installing the Renku app in the desired namespace (#3332).
- UI: Avoid unexpected redirects when clicking on the 2.0 dashboard session buttons (#3378).
Improvements
- UI: Update the Admin page to set up Connected services (#3332).
- Gateway: Add support for enabling debug logs from the gateway (#730).
Bug Fixes
- csi-rclone: Do not log potentially sensitive data in error messages.
- csi-rclone: Properly handle encrypted secrets with the new annotation-based storage class.
Renku 0.59.2 is a bugfix release that fixes a bug in Renku 2.0 where project editors could not edit project information.
🐞 Bug Fixes
- Data services: Allow project editors to send patches with the current namespace (#483).
- Data services: Allow project editors to send patches with the current visibility (#484).
Improvements
- Data services: Return 409 error when creating a project with a conflicting slug (#471).
- Data services: Change all serial id columns to be GENERATED AS IDENTITY (#461).
- Data services: Include
is_adminin the self/userendpoint (#472).
Bug Fixes
- Data services: Handle spaces in
provider_idfor connected services (#482). - csi-rclone: Do not log potentially sensitive data in error messages.
- csi-rclone: Properly handle encrypted secrets with the new annotation-based storage class.
Renku 0.59.1 is a bugfix release that improves stability and performance with renku notebooks when under heavy load.
Improvements
- Notebooks: Use gevent methods in notebooks api (#1996).
Renku 0.59.0 introduces the ability to reuse data connectors in multiple projects!
When you add a data connector (previously called a data source) to your project, you now have the new option to select other data connectors on RenkuLab,
for example those shared in your group, rather than having to re-enter the data connection details.
🌟 New Features
- UI: Add and re-use data connectors in Renku 2.0 projects (#3323).
✨ Improvements
- UI: Add a playful design for the 404 and application error pages (#3248).
- UI: Update redirect page styles (#3257).
- UI: Remove Renku 2.0 beta warning alert from dashboard (#3357).
🐞 Bug Fixes
- UI: Fix how permissions are checked in Renku 2.0, notably group members can perform actions according to their role in projects. (#3351).
- UI: Fix styles for the edit launcher environment list (#3360).
- UI: Allow opening a project from Renku 2.0 search if the namespace is missing in the result (#3353).
- UI: Fix update file and download buttons in Renku 1.0 (#3363).
New Features
- Data services: Add support for data connectors (#407).
- Data services: Do not synchronize blocked users from Keycloak (#393).
- Data services: Support getting permissions (#454).
- Notebooks: Add support for data connectors (#1991).
- Notebooks: Cache Amalthea sessions (#1983).
Improvements
- Data services: Handle errors in background jobs nicely (#463).
- Gateway: Add support for signing cookies (#734).
Bug Fixes
- Data services: Treat invalid JWT as 401 HTTP error.
- Data services: Change user preferences id sequence to proper value.
- renku-data-services 0.23.0
- renku-data-services 0.24.0
- renku-gateway 1.2.0
- renku-notebooks 1.27.0
- renku-ui 3.38.0
- renku-ui 3.39.0
- renku-ui 3.40.0
- renku-ui 3.40.1
Renku 0.58.1 fixes the correct handling of self-signed certificates in all the pods running OpenJDK as well as a bug
where some groups do not show up in search.
🐞 Bug Fixes
- Notebooks: Fix a bug where some docker images were found to not exist even when they really exist.
🐞 Bug Fixes
- Search: Fix a bug where some groups do not show up in search
- Notebooks: Forward authorization header when getting Gitlab tokens
- Notebooks: Only patch the jupyter servers once when migrating labels and annotations at startup
- Helm chart correctly handle self-signed certificates in all the pods running OpenJDK: - commit-event-service - event-log - knowledge-graph - search-api - search-provision - token-repository - triples-generator - webhook-service
Renku 0.58.0 fixes several issues related to Renku 2.0 search, and also squashes a bug where the
Renku 2.0 dashboard displayed content not related to you.
✨ Improvements
- UI: Polish Renku 2.0 pages and elements according to the latest design changes (#3254).
🐞 Bug Fixes
- Search Services: Resolve issues that caused items to be missing from Renku 2.0 search, including the search for members when adding members to projects and groups.
- UI: Resolve an issue where the Renku 2.0 dashboard displayed projects and groups that the user was not a member of (#3289)
- UI: Fix a bug where clicking on 'Show all my projects' on the Renku 2.0 dashboard redirected to a page displaying not only the user's projects but also others' projects (#3289)
- UI: Prevent glitches in the new session details sections (#3313).
Improvements
- UI: Update Storybook to show Renku 2.0 re-usable elements (#3254).
- UI: Add and edit connected services from the admin panel (#3329).
- Search Services: Allow to re-provision the index from data-services and as part of a SOLR schema migration
- Helm chart: Add RBAC for K8s cache for new AmaltheaSessions custom resource
- Gateway: Add extra credentials for the data service for the new AmaltheaSessions
- Gateway: Remove unused Python code
- Data services: Support event queue re-provisioning
- Data services: Support listing projects and groups by direct membership
🐞 Bug Fixes
- Data services: Do not use gather() in when listing projects
- Data services: Order resource classes by GPU, CPU, RAM and storage
- Data services: Following redirects when sending requests to git repositories
- Data services: Allow unsetting secrets for cloud storage
- Helm chart: Increase the connection timeout for the Authzed database health checks
- renku-search 0.6.1
- renku-ui 3.36.0
- renku-ui 3.37.0
- renku-ui 3.37.1
- renku-gateway 1.1.0
- renku-data-services 0.21.0
- renku-data-services 0.22.0
Renku 0.57.2 fixes several bugs in gateway and the csi-rclone driver.
Bug Fixes
- UI: show the correct repository access status
- Sessions: allow paused sessions with cloud storage secrets to resume normally
Bug Fixes
- Gateway: Fix path rewrite middleware when the path contains escaped characters (#726).
- csi-rclone: Correctly use OAuth2 tokens for cloud storage to enable mounting.
- csi-rclone: Remounting volumes created with older versions did not work.
Renku 0.57.1 fixes a bug in renku-ui-server where the service would be stuck in a crash loop when Sentry is enabled.
It also fixes two bugs in Notebooks related to the access token and shared memory in the user-sessions.
🐞 Bug Fixes
- UI: Access mode defaults to read-only when adding a new data source in Renku 2.0 (#3275).
- Notebooks: Don't fail clone process if access token doesn't exist (#1971).
- Notebooks: Fix shared memory attached to the JupyterServer container to be half of the total requested memory (#1984).
Bug Fixes
- UI: Fix the UI server being stuck in a crash loop at startup when Sentry is enabled (#3318).
- Gateway: Fix getting HTTP error 500 when logging in (#723).
Renku 0.57.0 brings a suite of new features and improvements to the Renku 2.0 beta. As a main highlight, you can now save and reuse the credentials for data sources. No more copy/paste on every session launch! We have also made small improvements to sharing, search, and sessions in Renku 2.0. For a full list of changes, see the list below.
NOTE to administrators: Upgrading the csi-rclone component will unmount all cloud storage for all active or hibernated sessions. Therefore, we recommend notifying your users ahead of time when you deploy this version of Renku and also if possible deploying the upgrade when there are fewer sessions that use cloud storage or just fewer sessions in general. Once the upgrade is complete users will be able to mount cloud storage as usual.
🌟 New Features
- UI: Support saving and managing credentials for Renku 2.0 data sources (#3266).
✨ Improvements
- Search Services: Enable searching by prefix of indexed words
- UI: Add members to groups and projects in Renku 2.0 by username instead of email (#3270).
- UI: Enable sharing search URLs by reflecting the search query in the URL for Renku 2.0 (#3245).
- UI: Show the status of a session via a dynamic browser tab icon (#3249).
- UI: Display session details in session page in Renku 2.0 (#3258)
- UI: Set default namespace when creating a new Renku 2.0 project (#3264).
🐞 Bug Fixes
- UI: Fix issue in Renku 2.0 where launched sessions did not use the default storage size of the selected resource class (#3295).
- UI: Fix misnomers on the group creation page (#3276).
- Data Services: Fix connected services showing errors for anonymous users
- Data Services: Fix 500 error being raised when modifying a session launcher
New Features
- csi-rclone: Read credential secrets from PVC annotations
- csi-rclone: Update the CSI sidecar container versions
- csi-rclone: Add support for decrypting data storage secrets.
- Gateway: The API Gateway components have been refactored and simplified (#709).
- Notebooks: Add a component for liveness detection
- Notebooks: Support for saving cloud storage secrets
Improvements
- Search Services: Reading all data service events from a single Redis stream. Processing from individual streams is kept.
- Data Services: Do not show user emails and use usernames instead for all interactions
- UI: The UI server has been refactored following the changes in the gateway (#3271).
Bug Fixes
- csi-rclone: Do not crash on unmounting as it might block dependent resources
- csi-rclone: Use extra storage class when reading secrets from a PVC annotation
- Data Services: Fix group member changes not being sent to search
- Data Services: Fix Redis not being able to connect to the master node
- csi-rclone 0.1.8
- csi-rclone 0.2.0
- csi-rclone 0.3.0
- csi-rclone 0.3.1
- renku-gateway 1.0.0
- renku-gateway 1.0.1
- renku-gateway 1.0.2
- renku-ui 3.34.0
- renku-ui 3.35.0
- renku-search 0.5.0
- renku-notebooks 1.26.0
- renku-data-services 0.20.0
Renku 0.56.3 fixes a bug in renku-data-services where strict user email validation
was causing problems with the admin panel and listing users.
🐞 Bug Fixes
- Data Services: do not validate user emails because Keycloak can contain invalid emails
Renku 0.56.2 fixes a bug in renku-data-services where a background job would stop working
if a deleted project wasn't correctly removed from the authorization database.
🌟 New Features
- Data Services: Adds endpoint for saving storage credentials
🐞 Bug Fixes
- Data Services: Fixes background job not working with Authzed db in inconsistent state
- Data Services: Fixes query args validation for /api/data/user/secrets endpoint
- Data Services: Splits error into 401 and 403 depending on the error
Renku 0.56.1 fixes a bug where Amalthea would not start when the prometheus metrics or the
audit log export functionality is enabled.
🐞 Bug Fixes
- Amalthea: Fix failing startup when prometheus metrics or audit log is enabled.
Renku 0.56.0 adds new features and improvements to several components.
🌟 New Features
- UI: Update incidents and maintenance banner and summary (#3220)
- UI: Add incidents and maintenance section in the admin panel (#3220)
- Data Services: Add platform configuration
✨ Improvements
- Revamp design for Renku 2.0 (#3214).
🐞 Bug Fixes
- Use standard HTML input fields for secret values (#3233).
Improvements
- Amalthea: Sessions can now run correctly on Kubernetes version 1.29.
🐞 Bug Fixes
- Amalthea: Fix the repository for the scheduler image in the Amalthea Helm chart.
- Amalthea: Properly load the namespace configuration when starting the operator.
- Amalthea: Fix the missing health check endpoint for the old operator.
- renku-data-services 0.18.0
- renku-data-services 0.18.1
- renku-ui 3.32.0
- renku-ui 3.33.0
- amalthea 0.12.0
- amalthea 0.12.1
- amalthea 0.12.2
Renku 0.55.0 introduces user and group pages in Renku 2.0, where you can see all projects owned
by those people. In addition, you can now fully take advantage of RenkuLab resources in Renku 2.0 by
setting a resource class for your session launchers.
🌟 New Features
- UI: Renku 2.0: Add user pages that show all projects in the namespace (#3198)
- UI: Renku 2.0: Extend group pages to show all projects in the namespace (#3198)
✨ Improvements
- UI: Renku 2.0: Provide clickable links between projects and user/group namespace pages on the project page and in search results (#3198)
- Search Services: Renku 2.0: Show creator name and project namespace in search results, where before only the respective ids were included (#3198)
- UI: Renku 2.0: Support setting a default resource class for a session launcher in Renku 2.0 (#3196)
Improvements
- Search Services: The search query is now accepted at
/api/search/queryurl path and a/api/search/versionendpoint has been added - Data Services: Change API to provide user and group pages in Renku 2.0
Renku 0.54.2 fixes a bug with testing the cloud storage connection for WebDAV.
🐞 Bug Fixes
- Data Services: Fix verifying cloud storage connection not working with WebDAV by correctly obscuring RClone values.
Renku 0.54.1 introduces a few bug fixes in the notebooks and data services components.
🐞 Bug Fixes
- Notebooks: Patch the correct environment variables when a session is resumed after being hibernated
- Data Services: Assign the correct project permissions to group members
✨ Improvements
- Test the cloud storage connection before persisting the configuration (#3194)
- Prompt for cloud storage credentials on v2 session start (#3203)
- Indicate repository permissions in Renku 2.0 (#3136)
🌟 New Features
- Secrets: Allow rotating the private key for secrets storage
🐞 Bug Fixes
- Search Services: Set keycloak url into the allow list of JWT issuer urls. This setting is now mandatory to the search-api service.
🌟 New Features
- Search Services: Enable admin to search without restrictions. Support for namespace search term in user query.
✨ Improvements
- UI: Convert font-awesome icons to bootstrap icons (#3173, #3161)
- UI: Improve membership maintenance UX in Renku 2.0 (#3154)
- UI: Small updates to the connected services page (#3149)
🌟 New Features
- Search Services: Adds a /version endpoint
🐞 Bug Fixes
- Search Services: Improve verifying JWT tokens using public key from keycloak
- UI: Show project members on the project information page in Renku 2.0 (#3143)
- UI: Fix project page nav in small view ports in Renku 2.0 (#3168, #3169)
- UI: Update session buttons in Renku 2.0 (#3172)
- UI: Update session badges on the project page of Renku 2.0 (#3174, #3175)
- UI: Redirect to group page after creation in Renku 2.0 (#3177)
- UI: Show a full page 404 when a group or project is not accessible in Renku 2.0 (#3162, #3176, #3153)
- UI: Fix updating project keywords in Renku 2.0 (#3187)
- Data services: Fix pagination on the
/namespacesAPI endpoint - Data services: Silence "Preferences not found for user" exceptions and stack traces
Renku 0.52.2 fixes a bug in Data Service.
🌟 New Features
- Data services: Add endpoint for repository permissions for connected services.
🐞 Bug Fixes
- Data service: Fix typing issue preventing the service from starting when sentry is enabled.
- Data service: Prevent removing all owners from Renku 2.0 resources.
Renku 0.52.1 fixes a few bugs in Renku 2.0, namely cases where:
- sessions could not start if the parent project listed zero repositories and one or more cloud storages to mount
- long running data migrations for user namespaces would cause the data service to keep restarting and never start
This release also includes minor improvements on the backend that will not be visible to users.
This release changes the name of the background jobs that synchronize
the data service with Keycloak and also changes the corresponding section for these jobs in the values file.
These jobs have a more general name because they will perform data migrations for the data service in addition to
synchronizing with Keycloak. This requires additional actions from administrators only if you are setting custom
values for dataService.keycloakSync in the values file, but in most cases the default images set in this
section will be used so no action will be required.
🐞 Bug Fixes
- Notebooks: Do not add storage mounts patches when a session has no repository (#1892)
🌟 New Features
- Data services: Configure trusted reverse proxies
- Data services: Send message queue events in a background process
- Data services: Run asynchronous code in database migrations
- Data services: Support PKCE for authentication with connected services
- Data services: Send group events to the message queue
🐞 Bug Fixes
- Data service: Do not perform data migrations for user namespaces at startup
- Data service: Remove leading underscores on route names
- Data service: Do not crash when a user that is already in a resource pool is added again to the same pool
Renku 0.52.0 introduces a new feature to save and use secrets in RenkuLab sessions.
For example, save your credentials for a database or external computing resource in
RenkuLab to access those external systems from a RenkuLab session. Save secrets via the
new User Secrets page in the account drop down, and choose which secrets to mount in a
session on the Start with Options page. More details on this feature can be found in the
[documentation](https://renku.readthedocs.io/en/stable/topic-guides/secrets/secrets.html).
Administrators can customize the culling times (the length of time before an idle session is paused or a paused session is deleted) for different resource pools.
This release also contains new features related to Renku 2.0. However, Renku 2.0 is still in early development and is not yet accessible to users. For more information, see our [blog](https://blog.renkulab.io/renku-2).
🌟 New Features
- Data Services: Add new secrets storage service for managing user session secrets, including new endpoints on data-service to manage these secrets.
- Data Services: Add the possibility for users to connect Renku 2.0 projects to external services, allowing users to clone, pull and push repositories e.g. from GitLab.com or GitHub.com.
- Notebooks: Add support for repositories from external services in Renku 2.0 sessions.
- UI: Add a new User Secrets page to manage secrets, and extend the session launch pages to select secrets to include in the session. (#3101).
- UI: Customize culling times for resource pools (#3113).
- UI: Introduce a new design for Renku 2.0 project pages (#3108).
- UI: Update the user interface to reflect changes to Renku 2.0 sessions (#3122).
- UI: Add support for Renku 2.0 authorization implementation and roles (3.27.0).
✨ Improvements
- Search Services: Add support for groups, namespaces and project keywords.
- UI: Introduce formal navigation for Renku 2.0 pages (#3095).
- UI: Use namespace/slug to identify Renku 2.0 projects (#3103).
🌟 New Features
- Data Services: Update the authorization for access to Renku 2.0 projects and groups to work with Authzed DB, a 3rd party database dedicated to saving authorization data and making authorization decisions
- Search Services: Support processing v2 schema messages (alongside with v1). Make the query parser more lenient to not raise parsing errors.
🐞 Bug Fixes
- Data Services: Allow removing tolerations and affinities on resource pools via PATCH requests
- renku-data-services 0.9.0
- renku-data-services 0.10.0
- renku-data-services 0.11.0
- renku-data-services 0.12.0
- renku-notebooks 1.23.0
- renku-notebooks 1.24.0
- renku-notebooks 1.25.0
- renku-search 0.1.0
- renku-ui 3.24.0
- renku-ui 3.25.0
- renku-ui 3.26.0
- renku-ui 3.27.0
Renku 0.51.1 fixes a bug where sessions were not considering the case (upper or lower) of the
project name that was being cloned when a session is started. This resulted in the working directory
being set to one location and the project cloned in another. This bug only affected projects where
users have manually changed their project paths to include uppercase characters or for projects that
were not created through Renku but were imported after creation.
🐞 Bug Fixes
- Notebooks: Use the case sensitive project name when cloning repositories at startup
Renku 0.51.0 introduces new features related to Renku 2.0. However, Renku 2.0 is still
in early development and is not yet accessible to users. For more information, see our
[roadmap](https://github.com/SwissDataScienceCenter/renku-design-docs/blob/main/roadmap.md).
- This release introduces groups to Renku 2.0.
- Various bug fixes and improvements
🌟 New Features
- UI: A new entity, groups, has been introduced to Renku 2.0. Groups are a way to organize projects in Renku 2.0.
- UI: Projects are always in a group -- either the user's implicitly-created group, or a group that has been explicitly created.
✨ Improvements
- UI Add an "email us" button below the session class selector to request more resources (#3073)
🐞 Bug Fixes
- Data service: Allow proper removal of users from resource pools
- Data service: Enable searching for all users when adding users to resource pools
🌟 New Features
Data services: Initial support for groups
🐞 Bug Fixes
Data service: Increase timeout for synchronizing Keycloak users
- renku-data-services 0.8.3
- renku-data-services 0.8.2
- renku-data-services 0.8.1
- renku-data-services 0.8.0
- renku-ui 3.23.0
- renku-ui 3.22.0
Renku 0.50.0 introduces several new features related to Renku 2.0. However, Renku 2.0 is still
in early development and is not yet accessible to users. For more information, see our
[roadmap](https://github.com/SwissDataScienceCenter/renku-design-docs/blob/main/roadmap.md).
- This release introduces new sew search functionality for Renku 2.0.
- Support has been added for interactive sessions in Renku 2.0 projects.
🌟 New Features
- UI: Renku 2.0 Search page with initial support for project and user search (alpha release)
- UI: Support for interactive sessions in Renku 2.0 projects, comprising global session environments and session launchers (alpha release)
- Notebooks: Initial support for Renku 2.0 sessions, supporting mounting multiple repositories (alpha release)
- UI: Add a new navigation top bar for Renku 2.0 (alpha release)
- UI: Add an ad-hoc feature flag for Renku 2.0 (alpha release)
✨ Improvements
- UI Update the footer links section with Mastodon (#3081, #3059)
- UI Improve session scheduling error messages (#3082, #3036)
🐞 Bug Fixes
🌟 New Features
- Data services: Initial support for project and user search for Renku 2.0 (alpha release)
- Data services: Add support for sentry and prometheus
- Search services: Initial support for project and user search for Renku 2.0 (alpha release)
- Data services: Initial support for Renku 2.0 session environments and session launchers (alpha release)
Improvements
- KG: Jena 5.0.0 upgrade
- renku-data-services 0.6.0
- renku-data-services 0.7.0
- renku-gateway 0.24.0
- renku-graph 2.50.0
- renku-notebooks 1.22.0
- renku-search 0.0.39
- renku-ui 3.21.0
This release contains minor bug fixes.
🐞 Bug Fixes
- Data services: Fix the incomplete synchronization of Keycloak users which caused problems with granting user access to resource pools
Improvements
- renku-ui: Visit the /api/data/user endpoint when a user is logged in (#3080).
The release contains bug fixes to renku core service related to project migration.
This release also contains initial support for next generation 'Renku 2.0' functionality. However, Renku 2.0 is still in early development and is not yet accessible to users. For more information, see our [roadmap](https://github.com/SwissDataScienceCenter/renku-design-docs/blob/main/roadmap.md).
Note for administrators: this release includes breaking changes due to upgrading PostgreSQL to 16.1.0. This requires modifying the values file to work with the new PostgreSQL Helm chart. Please check (the helm chart values changelog) for detailed instructions.
🐞 Bug Fixes
- Core Service: Fix issue with having to run project migration twice to migrate the Dockerfile/project template.
New Features
- Data services: Initial support for Renku 2.0 projects (alpha release)
Improvements
- csi-rclone: added rclone logs to regular node-plugin logs. (#11).
Renku 0.48.1 only changes how the Terms of Use and Privacy Policy sections
can be customized by administrators.
Renku 0.48.0 introduces the ability to add a Terms of Use and Privacy Policy to
RenkuLab, as well as an assortment of small improvements and bug-fixes.
🌟 New Features
- 📜 UI: Show terms of use and privacy policy in the help section (#2954).
✨ Improvements
- 🖌 UI: Improve appearance of templates on new project page (#2999).
- 🛑 UI: Unify appearance of project settings alerts (#3001).
🐞 Bug Fixes
- UI: Restore logged in/out notifications (#3014).
- UI: Hide button to add storage on deployments not supporting external storages (#3001).
- UI: Fix landing page parallax background (#3010).
- UI: Fix search bar styles (#3019).
- UI: Handle
jsonrpcimproper redirects (#3017, #2966).
Improvements
- Infrastructure: Upgrade the version of PostgreSQL to 16.1.0.
- UI: Add initial alpha implementation of Renku 2.0 projects (#2875).
This release only includes changes to the documentation and updates to the acceptance tests. It doesn't bring any new features or bug fixes.
This release expands Renku's cloud storage functionality in two key ways: First, mounted storages are now read and write, so you can use mounted storage as an active workspace for your data in a RenkuLab session. Second, we have expanded the cloud storage services you can integrate with RenkuLab. You can now mount not only S3 buckets, but also WebDAV-based storages and Azure Blobs.
If you use SSH sessions via the CLI, you can use cloud storage there too! Configure cloud storage for your project on RenkuLab.io, and those storages will be mounted in your remote session. Support for cloud storage in local Renku sessions is still on our roadmap.
This release also adds the ability to change which resource class your session uses when you unpause the session, in case the original resource class is now full.
🌟 New Features
- 🖋 Notebooks,Data Services,CSI: Support for read and write storage mounting in sessions using a new rclone based storage driver (#1707, #92, #1).
- 🔌 UI: add support for more storage services (#2908, #2915).
✨ Improvements
- 🖌️ UI: Improve the look and feel of the home page (#2968, #2937, #2927).
- 🔐 UI: Use password fields for credentials (#2920).
- 🔧 UI: Allow users to modify non running sessions (#2942).
- 🛑 UI: Improve feedback when starting sessions on outdated projects (#2985).
- 🖌️ UI: Update the Renku logo and Renku browser icons (#2848).
🐞 Bug Fixes
- UI: Resize the feedback badge on the session settings page (#2953).
- UI: Fix the environment dropdown on the Start session page (#2949).
- UI: Improve string validation when trying to upload a dataset file by URL (#2834).
Improvements
- UI: RenkuLab admins can now add tolerations and node affinities to resource classes (#2916).
- UI: RenkuLab admins can add multiple users to a resource pool at once via a list of emails (#2910).
- UI: Use the renku-core API for session options (#2947).
- UI: Specify a branch every time a renku-core API is invoked (#2977).
- amalthea 0.11.0
- csi-rclone 0.1.5
- renku-data-services 0.4.0
- renku-notebooks 1.21.0
- renku-ui 3.18.0
- renku-ui 3.18.1
- renku-ui 3.19.0
Renku 0.46.0 contains a bugfix for issues some users are facing when migrating projects to the newest metadata version.
✨ Improvements
- UI: Improve feedback when starting sessions on outdated projects (#2985).
- CLI: Allow specifying storage to mount when launching Renkulab sessions from the CLI (#3629).
- KG: Remove the Free-Text Dataset Search API as improved functionality is offered by the Entities Search. (#1833).
- KG: Add support for specifying
templateRefandtemplateParameterson the Project Create API. (#1837).
🐞 Bug Fixes
- Core Service: Fix migrations not working when the Dockerfile needs to be migrated as well (#3687).
✨ Improvements
- Core Service: Allow passing commit sha on config.show endpoint for anonymous users (#3685).
- Core Service: Removed support for metadata v9 projects in the UI. Migration to v10 is now required.
- Core Service: Fixed a bug where projects weren't cloned shallowly, leading to large projects not working properly on the platform.
🐞 Bug Fixes
- KG: The process removing expiring Project Access Tokens not to be locked on the date of rollout.
- UI: Use the default branch on all the core datasets API to prevent cache conflicts resulting in broken or missing datasets (#2972).
This is a bugfix release that updates the helm chart to work with new prometheus metrics in the renku core service, which was preventing it from starting properly if metrics were enabled. In addition this release also addresses problems with expiring Gitlab access tokens when sessions are paused and resumed which caused resumed session to not be able to push to Gitlab or also it caused some sessions to not be able to resume after they have been paused.
🐞 Bug Fixes
- Helm Chart: update core-service deployment to allow service and rq metrics to run side-by-side (#3303).
- Notebooks: use a larger /dev/shm folder in sessions (#1723)
- Notebooks: properly renew expiring Gitlab tokens when hibernated session are resumed (#1734)
- Gateway: properly renew expiring Gitlab tokens for hibernating sessions (#692)
Renku 0.45.0 adds support for pausing and resuming sessions from the CLI. You can now also specify a
project image when initializing a project from the CLI. Additionally, this release brings coherent usage
of Dataset name and slug across all Renku APIs.
✨ Improvements
- Core Service, CLI: Add support for specifying a project image during project initialization (#3623).
- CLI: Add support for pausing & resuming remote sessions from the cli (#3633).
✨ Improvements
- Core Service, CLI: Make slug and name consistent with rest of platform (#3620).
- Core Service: Add prometheus metrics (#3640).
- UI: Adapt dataset APIs to the new naming convention used in the backend (#2854).
- KG: All APIs to return Dataset
slugandnameand notitleproperty (#1741). - KG: Clean up process removing project tokens close to their expiration date (#1812).
Renku 0.44.0 introduces the ability to pin your favorite projects to the dashboard
in RenkuLab for easy access. Additionally, it features a redesigned landing page that
provides information about Renku, its key features, and the development team behind the
platform, plus entry points for getting started with the platform.
🌟 New Features
- 📌️ UI: Users can now pin projects to the dashboard, up to a maximum of 5 projects (#2898).
- 🎨 UI: Introduce a redesigned landing page to enhance the user experience for new users exploring the platform for the first time (#2925).
✨ Improvements
- 🖼 UI: [Keycloak] Enhance UX for registration and authentication in the platform (#26).
🐞 Bug Fixes
- UI: Correctly update progress of project indexing (#2833).
- UI: Change icons in the Nav bar to use Bootstrap icons (#2882).
- UI: Fixed bug that caused Dashboard to reload frequently by handling errors from the
getSessionsquery in the Dashboard (#2903). - UI: Adjust dropdown menus with anchors nested in buttons (#2907).
- UI: Update the workflows documentation link (#2917).
- UI: Add whitespace after author name in session commit details (#2921).
✨ Improvements
- Data services: New API endpoints to store and retrieve user preferences have been added to support the projects pins (#85).
Renku 0.43.0 brings improvements to the KG API, addresses a few bugs in the UI
and in the data services API.
A note to Renku administrators: this release includes breaking changes in our Helm chart values file.
For more details on the Helm chart values changes please refer to the explanation in helm-chart/values.yaml.changelog.md.
✨ Improvements
- KG: Performance improvements to the Cross-Entity Search API. (#1666).
- KG: The Cross-Entity Search API to allow filtering by a
role. (#1486). - KG: Improved search to return results where the search keyword is separated by underscores. (#1783).
- KG: A new
GET /knowledge-graph/versionAPI. (#1760). - KG: Token service and Webhook service can now accept an AES token that is not base64 encoded. (#1774).
🐞 Bug Fixes
- 🔽 UI: Prevent showing wrong options on the Session dropdown menu when the project namespace includes uppercase letters (#2874).
- 🔲 UI: Restore the switch between creating and importing a dataset, and restyle the buttons (#2857).
- 🔨 UI: Address visual glitches on many pages (#2883).
- 🧑🤝🧑 UI: Prevent occasionally duplicating last visited projects on the Dashboard (#2892).
- KG: Prevent CLI's Dataset Import from failing when the Dataset belongs to a project with more than 20 datasets.
Improvements
- KG: KG services to work with both
Base64encoded and ASCII secrets read from configuration. - KG: Java upgraded to 21.0 and Jena to 4.10.0.
Bug Fixes
- UI: Correctly handle Statuspage down (#2871).
- CRC: Do not create new quotas when updating existing ones
- CRC: Use one database connection pool with limited number of connections
- renku-graph 2.47.1
- renku-graph 2.47.0
- renku-graph 2.46.0
- renku-graph 2.45.0
- renku-graph 2.44.0
- renku-ui 3.15.1
- renku-data-services 0.2.3
Renku 0.42.1 is a bugfix release that addresses the following bugs in a few services:
- creating new resources in the
data-servicesAPI - properly enforcing access controls to the default resource pool
- accidentally removing the git repository directory from hibernated sessions
- properly templating node affinities and tolerations from the
data-servicesinto user sessions
Renku 0.42.0 allows RenkuLab administrators to easily manage user resource pools via an Admin Panel built into RenkuLab.
User resource pools are a way to manage the compute resources accessible to groups of RenkuLab users for interactive sessions.
From the new Admin Panel, admins can create resource pools, set their max resource quotas, customize the session classes
available within pools, and add users to pools. Admins can access the new Admin Panel by navigating to the account icon
in the top right in RenkuLab and selecting 'Admin Panel'. To access the Admin Panel, a user must have the renku-admin role
delegated to them in Keycloak.
In addition, the login screen was updated to better space components on smaller screens and fix minor visual glitches.
🌟 New Features
- 🖼 UI: Admins can configure compute resources available to groups of users for interactive sessions. (#2752).
✨ Improvements
- 💾 UI: Show a confirmation text when saving a session (#2856).
renku-gatewaycan now proxy to Keycloak endpoints
Renku 0.41.1 is a bugfix release to patch a bug found in the data service which prevented
new users from being created due to a db migration problem.
Renku 0.41.0 adds new functionality for configuring external storage in projects! Users can now
configure external storage to be mounted automatically in their sessions. The settings are persisted for the project,
but access control is managed by the provider of the storage, not by Renku. This means that for restricted
data sources, users must enter credentials separately. This first implementation only supports S3-compatible storage,
but we will add support for additional providers soon.
Lastly, with this release administrators can configure the RenkuLab homepage to highlight chosen projects.
A note to Renku administrators: this release includes breaking changes in our Helm chart values file.
Refer to the Internal Changes section below for more details.
🌟 New Features
- 🖼 UI: Admins can designate projects to be showcased on the home page, which will show them in the showcase section of the home page (#2799).
✨ Improvements
- 💾 UI: Add support for cloud storage configuration per project. There are now more options to customize to support external S3 and S3 compatible storage better (#2760).
- 🌈 UI: Improve color contrast and other UX elements (#2846).
This release is a breaking change to the Helm values file and it requires minor edits to the following field:
ui.homepageremoved the unusedprojectsfield and added theshowcasefield.amalthea.scheduler.*deprecates all existing child fields and adds new child fields. If you are not defining these fields in your values file then you are using the default Kubernetes scheduler and this requires no action. But if you are defining a custom scheduler in your deployment's values file then this requires additional edits to your values file so that you can retain the same functionality as before.- the
crcfield in the values file has been renamed todataService, all child fields remain the same functionally and by name.
For more details on the Helm chart values changes please refer to the explanation in helm-chart/values.yaml.changelog.md.
In addition to this, other notable changes include:
- add node affinities and tolerations for resource classes
- persist cloud storage configurations at the project level
- validation of Rclone cloud storage configuration by the backend
- update the Amalthea scheduler to work with newer versions of Kubernetes
renku-notebooksnow get S3 cloud storage configuration fromrenku-data-servicesrenku-gatewaynow provides credentials for the cloud storage potion ofrenku-data-services- UI shows prominent banners during major outages
- various bug fixes across many components
- users can be prevented from accessing the default resource pool in
renku-data-services
- renku-data-services 0.1.1
- renku-data-services 0.2.0
- renku-gateway 0.22.0
- renku-notebooks 1.20.0
- renku-ui 3.14.0
- amalthea 0.10.0
Renku 0.40.2 fixes a bug in the Renku data services where the web server consumed a lot of database connections.
🐞 Bug Fixes
- Data services: Run the server with only 1 worker so that fewer database connections are consumed
Renku 0.40.1 reverts recent changes to Lucene configuration in the Triples Store preventing users from searching by keywords.
🐞 Bug Fixes
- KG: Use the StandardTokenizer to allow searching by keywords containing underscore signs.
Renku 0.40.0 introduces UI performance improvements and fixes internal KG and Triples Store performance issues.
✨ Improvements
- 🚀 UI: Reduce the compiled bundle size to improve performance of the UI (#2818, #2827, #2832)
- 🚀 UI: [Dashboard] Speed up showing the warning for non-indexed projects (#2824)
- 🛠️ UI: [Projects] Use the KG API to update a project's metadata for the following cases: visibility, keywords and description (#2793)
🐞 Bug Fixes
- 🚀 KG: reduces the number of update queries run against the Triples Store causing its performance degradation.
- 🛠️ UI: [Datasets] Use versioned URL of renku-core when uploading files to a dataset (#2831)
Renku 0.39.3 fixes various bugs.
Bug Fixes
- Helm chart: fix problem with missing network policies preventing access to sessions
- Helm chart: use the session specific affinity, node selector and tolerations and not the general configuration reserved for Renku services
- Helm chart: use the correct default value for the Renku OAuth client in Gitlab
Renku 0.39.2 fixes a bug when pausing sessions.
🐞 Bug Fixes
- Renku Notebooks: fix a bug in session hibernation (#1645)
Renku 0.39.1 fixes bugs in the Helm chart introduced by 0.39.0.
This introduces changes in the templates and values file of the Helm chart from 0.39.0 that were causing the Helm upgrade operation to fail.
Renku 0.39.0 moves all renku component Helm charts to one single chart that now resides in this repository.
After initial testing we have noticed a bug in this version of the Helm chart. If you have already deployed this version simply
upgrading to 0.39.1 will fix things. If you have not yet deployed this version then skip it and go straight to 0.39.1.
The reason for the bug is that we replaced the spec.selector.matchLabels field of two important deployments in the Gateway
because of this the two components do not upgrade and the whole Helm upgrade operation fails.
Also, with the next releases we will adopt a specific way of versioning the helm chart. Namely:
- Patch changes (i.e.
0.50.1->0.50.2) indicate that there are NO changes in the Helm chart and that only application level bug fixes are present in the new release. - Minor version changes (i.e.
0.50.2->0.51.0) indicate that there are NO changes in the Helm chart and that only application level new features and/or application level breaking changes are present. - Major version changes (i.e.
0.50.0->1.0.0) will be reserved for changes in the Helm chart, either when the values file changes or when the Helm templates change.
Please note that this is a breaking change to the values file and it requires three minor edits to the following fields:
graph.jena.*moved tojena.*notebooks.amalthea.*moved toamalthea.*notebooks.dlf-chart.*moved todlf-chart.*
For more details please refer to the explanation in helm-chart/values.yaml.changelog.md.
There are now no more separate Helm charts for the core, notebooks, graph, UI and gateway components. All the Helm templates have been moved into the main Renku Helm chart in this repository.
Renku 0.38.0 improves the Knowledge Graph API, with a new Project Creation functionality and a Project Update enhancement.
There is also a new version of the core service with multiple bug fixes and a few new features.
✨ Improvements
- CLI: allow disabling automated parameter detection in renku run (#3548).
🌟 New Features
- 🖼️ Knowledge Graph: New Project Create API to create a project in GitLab and Knowledge Graph (#1635).
🐞 Bug Fixes
- Knowledge Graph: Improves quality of the results returned by the Cross-Entity Search API.
- Knowledge Graph: The Project Update API to work for non-public projects (#1695).
Improvements
- Core Service: replace/refactor internal repository cache (#3534).
Bug Fixes
- CLI: do not freeze/unfreeze plan view model (#3599) (3c48cff)
- CLI: simplify ssh setup and key usage (#3615) (3fa737a)
- Core Service: setting a non-existing config property to null more than once results in error (#3595) (e0ff587)
- Core Service: skip fast cache migrations check for anonymous users (#3577) (9ee3176)
- Core Service: normalize git url to avoid duplicate cache entries (#3606) (19142c6)
- CLI: adapt to changes in Knowledge Graph API for importing datasets (#3549) (020434a)
- Core Service: add branch to service cache path (#3562) (3800a38)
- Core Service: add support for using default values in template parameters (#3550) (d162392)
- Knowledge Graph: Various issues preventing Grafana dashboards not working. (#1717) (#1719).
Renku 0.37.0 introduces a new feature to pause sessions and later resume them exactly where you left off. All of your work in progress, including files, data, and environment changes not saved to git, are resumed right as you left them.
This feature replaces RenkuLab's branch-based auto-save mechanism. Most users do not have to do anything to transition from auto-saves to persistent sessions. However, if your last session went into an auto-save, you can still retrieve that work by using Start with Options and selecting your most recent auto-save branch. If your project contains auto-save branches that you do not need anymore, you can safely delete them.
🌟 New Features
- ⏸️ Renku Notebooks and UI: Support for pausing (i.e. hibernating) and resuming sessions (#1518) (#2686).
🐞 Bug Fixes
- UI: restore adding files by URL to datasets (#2800).
New Features
- Renku Notebooks: Use a new version of Amalthea which adds fields for culling hibernating sessions in the CRD.
- Renku Notebooks - Helm chart breaking change:
notebooks.culling.idleThresholdSecondsin the values file was renamed tonotebooks.culling.idleSecondsThreshold.
Renku 0.36.3 is a bug-fix release that solves a few issues with creating new
projects and datasets.
🐞 Bug Fixes
- UI: fix render loops in creating new projects; they were occasionally creating problems based on the specific fields filled in by the user. (#2788).
- UI: restore adding files to datasets on an outdated but supported metadata version (#2788).
- UI: do not error on dataset thumbnails pointing to an external URL (#2791).
- UI: prevent failures when unzipping files with a large number of elements on dataset creation (#2786).
Renku 0.36.2 is a bug-fix release that fixes a bug with running renku save from JupyterServer
session sidecars.
🐞 Bug Fixes
- Renku Notebooks: Fix a problem that prevented users from saving data via the UI in a session (#1620).
Renku 0.36.1 is a bug-fix release that includes the fixes from 0.35.2.
It also includes a few changes behind the scenes on how the UI interacts with backend components.
Improvements
- UI: Take advantage of Core Service API versions (#2764).
Bug Fixes
- UI: Fix bootstrap icons (#2772).
Renku 0.36.0 introduces an updated landing page layout to help new users explore
the platform for the first time. Thus, it implements a few bug fixes for the UI and Knowledge Graph.
🌟 New Features
- 🖼️ Knowledge Graph: Project Update API can update description, keywords and image (#1631).
✨ Improvements
- 📐 UI: Update the landing page for non-logged users to simplify discovering the platform (#2741).
🐞 Bug Fixes
- UI: Fix the Renku version on the footer (#2776).
Bug Fixes
- UI: Prevent using different repository URLs for the same project (#2766).
Renku 0.35.2 introduces a UI bug-fix to prevent overloading backend components
when using pre-filled template links.
Bug Fixes
- UI: Handle embedded template variables in project creation links (#2789).
Renku 0.35.1 introduces bug fixes in the compute resource control (CRC) service
and the gateway.
Bug Fixes
- Compute resource control: Fix erroneous validation errors with quotas (#22)
- Gateway: Sticky sessions null de-reference causing crashes (#673)
Renku 0.35.0 introduces new features in the UI and bug fixes in various components.
🌟 New Features
- 🫥 UI: Add a new section in the project settings to change visibility (#2648).
- 🔢 UI: Show the Renku version on the footer and add a new page to list the backend components versions. (#2703).
✨ Improvements
- 🫥 UI: Use the description from the project metadata in the project pages. This means the description set at project creation won't go lost. (#2631).
- ❓ UI: Use a more generic and user-friendly concept instead of "Knowledge Graph" when referring to the project metadata processing (#2709).
🐞 Bug Fixes
- UI: Allow navigating back during and after the login without ending in a corrupted state (#2711).
- UI: Sort project datasets by the user-friendly title instead of the hidden name (#2702).
- UI: Update the loader spinner to fix DOM nesting errors (#2750).
- UI: Prevent fake warnings from memory constraints when starting sessions (#2757).
Improvements
Bug Fixes
- Core Service: Fix issue with cache.migrations_check timing out. (#3597) (20b5589)
- Core Service: Fix dataset image IDs for datasets imported from Zenodo (#3596) (f624b2b)
- Core Service: Fix issue on workflows UI with badly formatted IDs (#3594) (c418c17)
- Gateway: properly use Redis sentinel client (#668) (5ab4447)
- Gateway: properly redirect from /gitlab urls (#669) (2fac96f)
- Gateway: return 404 if the core service metadata version does not exist instead of redirecting to the endpoint that is using the latest metadata version (#667) (2753d07
- UI: Use a common project URL when invoking renku-core APIs (#2722).
Renku 0.34.1 fixes Project names in the UI and the Knowledge Graph API.
🐞 Bug Fixes
- Knowledge Graph: The Knowledge Graph APIs return wrong names, especially for Projects that are forks. (#1662).
Renku 0.34.0 comes with improvements in the Infrastructure.
New Features
- Infrastructure: add support for ingress class name
Improvements
- Documentation: refactor certificate management part to show how to make use of cert-manager and manually created certificates in both development and production contexts.
Renku 0.33.1 introduces bug fixes and addition of a warning field when listing servers in the Notebook service.
The minor change in the Notebook service API are fully backwards compatible.
It also brings some improvements and bug fixes in the Knowledge Graph.
✨ Improvements
- 🔎 Knowledge Graph: all the APIs return a new Project slug property. The path property although still available will be removed in the future. (#1641).
🐞 Bug Fixes
- Knowledge Graph: Cross-Entity Search cannot find projects by creator. (#1656).
Bug Fixes
- Renku Notebooks: parse old server options in request to start sessions (#1570) (8b3e5c0)
- Renku Notebooks: properly recover LFS files from autosave branches (#1568) (8f34b09)
- Knowledge Graph: fix for an infinite retry loop while sending certain types of internal events. (#1650).
Renku 0.33.0 introduces improvements and bug fixes in the UI and Knowledge Graph.
The UI benefits from better error handling and overall behavior, including improved handling of common R file extensions. Regarding the Knowledge Graph, the Cross-Entity Search improves significantly its performance and project visibility can be changed through a dedicated API.
🌟 New Features
- 🫣 Knowledge Graph: Add a new Project Update API for changing Project visibility (#1611).
✨ Improvements
- 🔎 Knowledge Graph: The Cross-Entity Search returns a new
dateModifiedproperty for Project and Dataset entities (#1612) and (#1595). - 〽️ Knowledge Graph: Improved performance of the Cross-Entity Search while searching for datasets (#1591).
- 🔙 UI: Add a global error page for fatal errors preventing blank pages (#2604).
- 📄 UI: Support previewing additional common R file extensions (#2639).
🐞 Bug Fixes
- UI: Prevent showing endless loader when migration errors occur (#2650).
- UI: Do not expand folders by default in dataset view when dataset contains large number of elements (#2628).
- UI: Render Rstudio components correctly -- sometimes columns were collapsed (#2660).
- UI: Prevent losing work when editing datasets (#2628).
New Features
- Renku Notebooks: Use a new version of Amalthea which adds fields for hibernating sessions in the CRD.
Bug Fixes
- Knowledge Graph: Fixed the problem of concurrent writes to the Triples Store causing data integrity violations (#1577).
Renku 0.32.0 introduces improvements in the KG services, enhancing KG overall performance.
✨ Improvements
- 🔁 KG:
updatedAtrenamed todateModifiedon the Project Details API (#1582). - 📖 KG: Improved performance of the Project Status API (#1554).
** Improvements**
- KG: A new process to synchronize various project properties between GitLab and Triples Store (#1569).
Renku 0.31.0 introduces the compute resource control (CRC) service, enabling
Renku administrators to manage access to specific computing resources. The
service exposes an HTTP API for the administrators to interact with. In this
way, Renku administrators can create, update or delete resource pools, and can
add to or remove users from resource pools. Please note that a user interface
for the CRC has not been added yet but it will be added in a future release.
Currently, the only way for administrators to interact with the CRC service is
through the swagger page which can be found at the path
/swagger/?urls.primaryName=crc%20service appended to the base URL of a Renku
deployment. A Renku administrator is any user who has the renku-admin realm
role. Assigning users to this role can be performed by the Keycloak
administrator via the Keycloak UI or API.
The CRC service also brings changes to the user interface for launching sessions, specifically when it comes to selecting compute resources for a specific session. With this version we have grouped different pre-set configurations of memory, CPU, RAM and GPU in resource classes. Resource classes are further grouped in resource pools and users are asked to select the resource pool and class they wish to use when they launch a session rather than separately specify memory, CPU, RAM and GPU requirements. The selection for the amount of disk storage required is also changed but now has more freedom than before. Users can now select disk storage with a slider that only has a maximum limit and no pre-set steps. For projects where the users have specified resource requests in the project settings the UI will provide hints as to which resource classes are suitable based on the settings. When the quick launch button is used to start a session the closest equal or greater resource class based on the project settings will be automatically selected.
Apart from the changes needed to support compute resource access features, support has also been added for common R file extensions.
This release also includes a hotfix for an issue with the horizontal scaling of the core-service where users could get redirected to the wrong service instance and subsequent requests to the core-service would fail due to partial cache misses.
🌟 New Features
- 🧑💻 UI: Update session start options and project settings to use compute resource pools (#2484).
🐞 Bug Fixes
- 〽️ UI: Support common R file extensions (#2638).
- 🛠 Renku Core Service: Isolates core-service cache per instance, improves cache cleanup. (#3555).
🌟 New Features
- Infrastructure: Add the compute resource control service.
- Renku Notebooks: Use the compute resource control (CRC) service.
Renku 0.30.1 is a small bugfix release that addresses a problem with the gateway Helm chart.
🐞 Bug Fixes
- Gateway: Remove duplicate environment variables in reverse proxy container (#660).
Renku 0.30.0 adds the ability for the core service to horizontally scale and for the gateway to provide sticky sessions
for the core service. In addition, improvements and bug fixes are also included on the UI, as well as required changes for
enabling sticky sessions for the core service.
🌟 New Features
- 🔭 UI: Surface backend error message on dataset list page (#2629).
🐞 Bug Fixes
- UI: Do not query for datasets if no backend is available for the project version (#2636).
🌟 New Features
- Gateway: Add sentry to reverse-proxy (#654)
- Gateway: Core-service sticky sessions (#646)
- Renku Core Service: Horizontal scaling (#3178).
- UI: Handle responses from the new core versions endpoint (#2134).
🐞 Bug Fixes
- Renku Core Service: Fixes importing private datasets in deployments with external gitlab (#3523).
- UI: Prevent API failures for projects on older metadata versions (#2627).
Renku 0.29.0 introduces new UI features and a PostgreSQL DB for triples-generator.
🌟 New Features
- 📝 UI: Add a customizable message to the dashboard page (#2592).
🐞 Bug Fixes
- UI: Restore deleting datasets (#2607).
- UI: Improve showing the error details for sessions (#2611).
- UI: Fix sessions not showing on dashboard (#2608).
- UI: Allow up to 100 namespaces and sort them (#2606).
- UI: Prevent crashes when handling markdown files (#2597).
✨ Improvements
- KG: A PostgreSQL DB is added for the triples-generator (values changelog).
Bug Fixes
- Infrastructure: properly generate PostgreSQL secrets on upgrade (#3137).
Renku 0.28.1 resolves a minor bug that occurs when launching sessions when git submodules are used.
Bug Fixes
- 🛠 Renku Notebooks: do not fail session launch if Git submodules couldn't be pulled.
Renku 0.28.0 simplifies the project status update by making it available in the project settings tab and improves the information in the UI regarding the indexing processes. Thus, it enables new features for the command line interface related to sessions and exporting dataset keywords.
Read on for a full breakdown of all new features, improvements and bug fixes included in this release.
🌟 New Features
- 🐳️ CLI: Pass docker run args to session start (#3487).
- 👩💻️ CLI: Shell completion for sessions (#3450).
- 📎️ CLI: Export dataset keywords (#3454).
- KG: Dataset Details API response enhanced with info about project specific dataset identifier (#1546).
- KG:
slugas a copy ofnameon responses from all Dataset APIs (#1544). - 🗑️ UI: Added a delete project button on the settings tab (#2416).
✨ Improvements
- 👩💻️ UI: Major rework and simplification of project status page (moved to Settings -> General) (#2315).
🐞 Bug Fixes
- 📎️ CLI: Fixed dataset update with external files (#3379).
- 🛠️ CLI: Fixed special paths in workflow files and bump
toil/cwltool(#3489). - 🖼️ UI: Made text not selectable in entity cards (#2546).
- 📎️ UI: Fixed the "add dataset to project" feature (#2549).
- 🔗️ UI: Fixed clicking on a file name on the dataset view wrongly leading to lineage and not contents (#1270).
- 🔗️ UI: Fixed getting a 404 page when switching from lineage view to contents (#2571).
✨ Improvements
- 🛠️ Gateway: Added new path to knowledge-graph webhooks (#639).
🐞 Bug Fixes
- 🛠️ Core: Fixed working on branches in the
core-svc(#3472). - 🛠️ Core: Return proper errors on migrations check (#3334).
Renku 0.27.0 upgrades the Keycloak version that is shipped with the project.
NOTE: make sure to check helm-chart/README.rst and helm-chart/values.yaml.changelog.md for instructions on how to upgrade to this version of Renku.
Improvements
- Infrastructure: (BREAKING CHANGE) Use a new Keycloak Helm chart (codecentric/keycloakx) and upgrade Keycloak to 20.0.3. This requires modifying your current values file to work with the new Keycloak Helm chart, see (the helm chart values changelog) for instructions.
Renku 0.26.2 resolves bugs and adds minor features in renku-graph.
✨ Improvements
- KG: Improved performance when searching for Projects.
Bug Fixes
- KG: Excessive Project Access Tokens creation when calling Project Status API for non-activated projects.
Renku 0.26.1 comes with a fix for KG services failing on startup when longer than 16 chars secrets are configured.
Renku 0.26.0 resolves bugs and adds minor features in the core-service, CLI, renku-graph, and the UI.
🌟 New Features
- 🚢 Renku CLI: Allow force-building local images and setting local port on docker session provider.
- KG: A new Recently Viewed Entities API giving information about entities the user viewed.
- 🔁 UI: Add a clone button to the project overview (#2495).
✨ Improvements
- ☝ Renku CLI: Removed nagging about new Renku CLI versions when running commands.
- 🪣 Renku CLI: Added support for storing dataset S3 credentials per bucket.
- KG: Improved quality of search results returned by the Cross-Entity Search API.
🐞 Bug Fixes
- 🛠 Renku Core Service, Renku CLI: Fixed an issue with v10 metadata migration regarding datasets.
- 🍎 Renku CLI: Fixed compatibility with Python 3.11 on MacOS.
- 🍎 Renku CLI: Fixed properly exporting triples for deleted datasets.
- 🛠 Renku Core Service, Renku CLI: Improved handling of Dockerfile changes when updating project template.
Improvements
- 📜 Renku Core Service, Renku CLI: Added code contracts in key places to ensure metadata consistency.
Bug Fixes
- KG: Fix KG services failing on startup when longer than 16 chars secrets configured.
Renku 0.25.6 fixes a bug in the Renku release process and does not bring any functional changes.
Renku 0.25.5 comes with a few KG bug-fixes.
🐞 Bug Fixes
- KG: Prevent presenting misleading information about Knowledge Graph integration status on projects where the user is not one of the members.
Bug Fixes
- KG: Resolve token decryption issues preventing Knowledge Graph integration activation.
Renku 0.25.4 introduces several KG and UI bug-fixes.
🐞 Bug Fixes
- UI: Prevent flashing a spinning wheel when loading workflows (#2493).
- UI: Restore the flag to show inactive workflows (#2502).
- UI: Prevent infinite spinning wheel when accessing projects by numeric ID without the required user's permissions (#2476).
- UI: Fix an issue where a notebook would not automatically open in a session for anonymous users as an anonymous user (#2479).
- UI: Prevent content layout shift when selecting a template (#2482).
- UI: Update broken documentation link (#2497).
Bug Fixes
- KG: Resolve issues with synchronization of project user access authorization data.
- KG: Ensure that the Delete Project API works when there is no data for the project in the Triples Store.
- KG: Ensure that the Lineage API works in cases of implicit parameters, inputs and outputs.
- UI: Correct handling of notebook search parameter with autostart (#2469).
Renku 0.25.3 introduces a bug fix in the Helm chart for the gateway.
Bug Fixes
- Gateway: chart: properly template horizontal pod auto-scaler for reverse proxy (#643).
Renku 0.25.2 introduces a few bug fixes and improvements in the UI.
✨ Improvements
- 🧾 UI: Use drop-downs for session options with many elements (#2461).
🐞 Bug Fixes
- UI: Prevent dropping valid pinned images when starting new sessions (#2466).
- UI: Ignore deleted projects on the dashboard (#2465).
- UI: Fix fork suggestion when trying to start sessions on non-owned projects (#2465).
- UI: Remove conspicuous commas in the add dataset screen (#2472).
Bug Fixes
- UI: Do not query workflows on outdated projects (#2460).
- UI: Fix broken warning component on sessions pages (#2474).
Renku 0.25.1 introduces a small bug fix in the Gateway internal components.
Bug Fixes
- Gateway: correct path for reaching Gitlab from the CLI, it should be
/reposinstead of/api/repos.
Renku 0.25.0 introduces an update to the base images and templates, as well as changes in internal components and the Helm chart.
Improvements
- New base images correct a
PATHmisconfiguration that occurs when connecting to a session with SSH. If using sessions through SSH, please update your project!
Improvements
- Gateway: replace the Traefik reverse proxy with a custom solution based on the Echo library in Go.
Renku 0.24.4 resolves bugs in the Knowledge Graph backend processes.
Improvements
- KG: Collect info about users who showed interest in projects and datasets.
Bug Fixes
- KG: Resolve problems causing flows accessing GitLab API to go into deadlock.
Renku 0.24.3 resolves bugs in the UI and in the Knowledge Graph backend processes.
🐞 Bug Fixes
- 🔗 UI: Resolve an issue where the Connect button on the Dashboard leads to a broken link (#2444).
Improvements
- UI: Retrieve project metadata from the KG on project access (#2414).
Bug Fixes
- KG: Resolve problems causing particular flows to terminate prematurely, as well as improve the quality of logging within the Activation API.
Renku 0.24.2 introduces bug fixes. We squashed a bug where you may have had trouble
finding your projects in other namespaces. Now, all projects show up in the Knowledge Graph
activation page so you can add them to your dashboard.
✨ Improvements
- ❌ Knowledge Graph: Add a new API to delete projects.
- 🔘 UI: Provide the same options on the session dropdown buttons across the dashboard and the project page. (#2393).
- 📖 UI: Make the browser column and file content column sticky when scrolling long files on the file viewer. (#2412).
- 🧾 UI: Improve the feedback for sessions ending in an error state. (#2411).
🐞 Bug Fixes
- Core Service: Fix a crash when migrating to v10 metadata (#3359).
- Knowledge Graph: Expand the Knowledge Graph Project Activation page to list all projects where the user is a member, not only owned projects.
- Sessions: Fixed bug where sessions from one project would appear under another project (#1423).
- UI: Prevent listing projects twice on the dashboard (#2408).
- UI: Start sessions with base images when pinned images are missing (#2410).
Improvements
- Knowledge Graph: A new functionality to capture Project viewing events
Renku 0.24.1 introduces bug fixes.
🐞 Bug Fixes
- Core Service: Correctly update Dockerfile on migration (#3351).
- Renku CLI: Fix git credentials helper setup in
renku login(#3348). - Sessions: Sessions crashing when automated token refresh runs in background (#1416).
Bug Fixes
- Knowledge Graph: Fixes and improvements to the schema v10 migration
Renku 0.24.0 introduces two new features: SSH-access to RenkuLab sessions
and a new RenkuLab Dashboard!
Would you like to work on your Renku project from the comfort of your own local computer? Use the Renku CLI to start an SSH session on RenkuLab, and open that session in your local terminal or even your IDE, such as VSCode. Check out the "Connect with SSH" option in the Session Start menu to get started, or see our docs. Note that SSH functionality must be enabled by your administrator and may not be available on all RenkuLab deployments.
And, your RenkuLab Dashboard now has a snazzy new look that puts your most used projects, sessions, and datasets at your fingertips. Quickly pick up where you left off: connect to your already-running sessions, start a new session on a recently visited project, or access your datasets- all from a single page!
Read on for a full breakdown of all improvements and bug fixes included in this release.
🌟 New Features
- ⌨️ Renku CLI: Enable connecting to RenkuLab sessions via SSH (#3318).
- 📑 UI: Show instructions on how to connect to RenkuLab sessions via SSH from the Session Start menu (#2376).
- 🧑💻 UI: Add a new dashboard for logged-in users, showing running sessions, last accessed projects, and own datasets (#2332).
✨ Improvements
- Sessions: Fail when injecting env vars that already exist in session (#1396)
- 📜 UI: Show commit messages in the commit selection dropdown when starting a session from a specific commit (#2362).
- 🔗 UI: Make searches shareable by storing parameters in the URL (#2351).
- 📸 UI: Customize avatars when creating a project (#2331).
🐞 Bug Fixes
- Gateway: Use offline access tokens for automated access from within sessions. (#632).
- Sessions: Propagate environment variables for R-Studio sessions (#1339).
- UI: Fix markdown problems with underscores in links and math formulas (#2374).
- UI: Restore session autostart when connecting from the notebook preview page (#2344).
- UI: Improve dataset pages (#2318, #2357).
- UI: Sort commits by date to prevent random order (#2347).
Improvements
- Core Service: Metadata v10 support
- Knowledge Graph Add support for the new Renku Metadata Schema v10.
- Knowledge Graph Enable the Cross-Entity Search API to allow multiple sort parameters.
- Knowledge Graph Remove deprecated GraphQL API
- Knowledge Graph: Upgrade Jena to 4.7.0
- Sessions: Show if ssh is enabled in /version of notebook service (#1407).
- Sessions: Introduce experimental Azure Blob storage support (#1374).
- Sessions: Enable SSH access via jump host (#1389).
Bug Fixes
- Sessions: Cloning the correct SHA for anonymous user sessions (#1406).
- amalthea 0.6.1
- renku-gateway 0.18.1
- renku-graph 2.28.0
- renku-notebooks 1.15.0
- renku-python 2.0.0
- renku-python 2.0.1
- renku-python 2.1.0
- renku-python 2.2.0
- renku-python 2.3.0
- renku-ui 3.2.0
- renku-ui 3.3.0
Renku 0.23.0 introduces the Renku Workflow File, a friendlier way to encode and run your data analysis pipelines
on Renku. You can write out your workflow in this easy-to-use YAML file, and execute it with renku run workflow.yml. Add a workflow
to your Renku project with our docs here!
🌟 New Features
- 📝 Renku CLI: Add support for workflow files which can be executed directly, greatly improving the UX around workflows (#3176).
✨ Improvements
- ⚙️ Renku CLI: Made toil the default workflow backend instead of cwl (#3220).
- 💨 Knowledge Graph: Performance improvements for Cross-Entities Search and Project Details APIs.
- 🔌 UI: Change text on the quick-start session button from "start" to "connect" when a session is running (#2268).
🐞 Bug Fixes
- Renku CLI: Fixed
toildependency not being installed correctly. - Renku core service: Fix issue with project templates being cached and users being unable to create projects based on the newest version of a template (#3243).
- UI: Restrict visibility options to be compatible with namespace and parent project in fork dialog (#2299).
Improvements
- Infrastructure Components:
redishas been upgraded from version6.0.5to7.0.7 - Knowledge Graph: New provisioning process managing data to be used in the future for further performance improvements of the search APIs.
Renku 0.22.0 introduces a simplified and more powerful search, now
powered by the Renku Knowledge Graph. Use the single integrated search bar
to discover projects and datasets across Renku.
Plus, after a few months away, Project and Dataset images are back! Upload an image to your project or dataset (via the Settings menu) to add some pop to your Renku project. You'll notice this change comes with a more compact look to Project and Dataset page headers, too.
Read on for more detail on UI and Knowledge Graph improvements and bug-fixes included in this release.
✨ Improvements
- 🔎 UI: Introduce a new cross-entity search page for searching Projects and Datasets simultaneously. This search page replaces the separate Projects and Datasets pages (#1894).
- 🔲 UI: Improve styling of buttons with menu and group buttons (#2243, #2284).
- 🖼️ UI: Restore projects and datasets avatars, and add a simple image editor. (#2231, #2246).
- 📊 UI: Update real-time the project's indexing status (#2255).
- 📑 UI: Update documentation links and target the stable release (#2276).
🐞 Bug Fixes
- UI: Restore per-language source highlighting in the file preview (#2233, #2265).
- UI: Limit the available namespaces in which new projects may be created to the ones owned by the user to prevent failures (#2187).
- UI: Prevent interface from freezing when interacting with broken sessions (#2269).
- UI: Remove idle time when moving to step two on the starting session page. (#2282).
Improvements
- Gitlab: Modify embedded renku-gitlab helm chart to use internal redis.
- Knowledge Graph: List project images on responses from Cross-entity search and Project details APIs.
- Knowledge Graph: Return more accurate processing details from the Project status API. The payload was updated and contains breaking changes).
- Knowledge Graph: Accept project-id query parameter on the Event log API.
- Knowledge Graph: Allow for greater control on the re-provisioning triggering conditions.
- UI: Reduce unnecessary components re-rendering.
- UI: Refresh the documentation for developers and external contributors (#2275).
Renku 0.21.0 brings tidings of tweaks and bug fixes to make your Renku experience a little bit smoother.
✨ Improvements
- 🎨 UI: Improve the layout of the project creation, session start, and file browser pages.
🐞 Bug Fixes
- 📃 UI: Update broken links to local projects and documentation, and add more links to useful resources (#2199, #2207, #2209).
- 🚀 UI: Fix glitches with autosave and improve layout of session pages (7fbda29, #2211).
- 🔦 UI: Prevent flashing inputs when forking a project (#2157).
Improvements
- Gateway: Add endpoint for refreshing expiring GitLab tokens
- Knowledge Graph: Improve functionality to refresh access tokens before expiration
- Knowledge Graph: Enhance migration functionality to restore missing CompositePlans
- Knowledge Graph: Fix to prevent data corruption which could previously occur due to duplicate Project creation dates
- Sessions: Check LFS size and available disk space before cloning
- UI: Receive notifications through WebSocket when session state changes (#2145, #2189).
Bug fixes
- Gateway: Do not remove Redis clients on logout
- Gateway: Address security vulnerabilities
- Knowledge Graph: Switched to the latest Alpine Linux to address docker image vulnerabilities identified by Snyk
- Knowledge Graph: Handle cases when Plan Invalidation Time is wrong
- Knowledge Graph: Make the Cross Entity search API results sorting case-insensitive
- Knowledge Graph: Escape Lucene keywords from Cross-Entity Search query parameter
- Knowledge Graph: Return all inactive Projects from the User's-Projects API (previously only returned 20)
- Sessions: Handle expiring GitLab tokens
Renku 0.20.0 tidies up the RenkuLab session start sequence, as well as an assortment of improvements and bug fixes.
✨ Improvements
- 🚀 UI: We tidied up the session launch sequence to have a unified appearance, regardless of where on RenkuLab you start your session from. Sessions also have better logs and error handling.
- 🎨 UI: The RenkuLab login and logout pages have been updated with the latest styling.
- 💬 Renku CLI: When you run
renku savein a clean but unpushed repository,renkunow informs you that it has pushed changes to the remote, rather than just saying that there were no changes to save.
🐞 Bug Fixes
- 💔 Renku CLI: Fixed an issue where
renku workflow composewould breakrenku workflow list. - 🍴 UI: Fixed the Project name field getting reset when forking a project.
- 📃 UI: Fixed issues with downloading session logs.
Improvements
- Knowledge Graph: Read lineage data from the new dataset in the Triples Store
- Knowledge Graph: Added info about Composite Plans to the Cross-Entity Search API
- Knowledge Graph: Adopted
renku-python 1.10.0with significantly improved graph export performance - Renku core service: Extended the workflow API, adding an
exportendpoint that returns the workflow definition. - Sessions: Added support for running sessions in a separate namespace
- Sessions: Added caching for Jupyter servers
Bug fixes
- Gateway: Removed trailing slash from redirect links
- Knowledge Graph: Fixed wrong Plans creation dates through migration
- Knowledge Graph: Switched to using Project Access Tokens for accessing GitLab API
- Renku core service: Fixed Plans creation dates from preceding their corresponding Activities
- Sessions: Fixed properly accept getting session logs without a limit
- renku-gateway 0.17.0
- renku-graph 2.22.1
- renku-graph 2.22.2
- renku-graph 2.22.3
- renku-graph 2.23.0
- renku-graph 2.24.0
- renku-python 1.9.3
- renku-python 1.10.0
- renku-ui 2.12.0
- renku-ui 2.13.0
- renku-notebooks 1.13.0
Version 0.19.1 is a minor bugfix release to the UI. In certain situations, the session save and refresh buttons would report that they were not supported, when in fact they would have worked. This problem has been fixed.
- UI: improve robustness of sessions save 💾 and refresh 🔄 buttons (#2100)
This release adds support for showing workflows in the UI. You can visualize workflows in project pages by clicking on the new Workflows tab. Support for editing workflows and searching them through multiple projects will come in a feature release.
This also brings changes to the way data is organized in the Triples Store and bug-fixes to improve the core service stability.
- UI: browse and visualize workflows in projects 🔀 (#2038)
- UI: add refresh button to update live sessions ↪️
- Renku core service: add
/workflow_plans.listand/workflow_plans.showfor listing and showing workflows in a project 🔀 - Knowledge Graph: use Named Graphs dataset in the Triples Store for provisioning processes and APIs 💾
- UI: fill values correctly in new project form links 🔗 (#2026)
- UI: handle corrupted autosave information and improve warnings when starting a session
⚠️ - Renku core service: fix intermittent issue with project cache concurrency 🏃
- Renku core service: fix import of private datasets with some cloud-native github instances
⤵️
This release fixes a bug in the core-service and includes improvements for the renku gateway service
- Gateway: enable
/gitlabpath even when external GitLab is configured, and forward traffic to external GitLab
- Renku Core Service: fix temporary working directory in service getting accidentally removed by other threads
- Project templates: fix broken
nbconvertpackage needed by jupyter notebooks and server
This release fixes a bug in sessions.
- UI: prevent occasionally flashing a loader when working with sessions
This release brings improvements and bug fixes to Renku UI.
- UI: Save session button (#1957, #1985, #2040)
- UI: Add environment variables when starting a session (#2058, #2066)
- UI: Add progress indicator when starting a session (#1879, #2054)
- Sessions: Detailed session start status breakdown (#1289)
- Renku Core Service, Renku CLI: Fixes Dockerfile Renku version when force setting a template to update an old project
- Renku CLI: Allow passing in multiple custom metadata entries for Project and Dataset entities
- Knowledge Graph: fixes improving stability
- UI: Restore notebook rendering (#2052)
This release includes fixes and improvements for the renku gateway service that deals with authentication It also includes improvements to the renku documentation about CLI plugins
- Documentation: add CLI plugins section
- Gateway: re-initialize keycloak server-side client if needed
- Gateway: remove anonymous user ID creation because it is handled by the ui-server
- Tests: Modify acceptance test wait duration for locating a terminal in a session
This release comes with the first step towards a new data organization inside the Renku Knowledge Graph. Although completely transparent for the users at this point, the change brings substantial additions to the internal processes within the Knowledge Graph as well as adds a migration which copies all the data in the old format to the new one. For the time being, data in both the new and the old format will be kept in sync, however the API will still use the data in the old format.
- Knowledge Graph: new parallel processes to provision data to Named Graphs datasets in the Triples Store
- Knowledge Graph: a new Triples Store migration that creates transformed version of all the data in the new Named Graphs dataset
- Knowledge Graph: Jena upgraded to 4.6.1 to address an issue that in certain circumstance makes Jena unresponsive
- Sessions: various bug fixes and improvements
This release brings improvements and bug fixes to renku-ui and renku-notebooks.
- UI: reduce unnecessary 'project locked' notifications (#1982, #2025)
- UI: expose project metadata as JSON-LD (#1867, #2022)
BREAKING CHANGES!
The renku-ui helm chart was restructured:
* the field ui.baseUrl was moved to ui.client.url
* the field ui.gatewayUrl was moved to ui.gateway.url
Consult the values changelog file for details.
The way anonymous sessions are handled has changed, and this means that an anonymous session that was started before the upgrade will no longer be accessible afterwards. You may want to notify users in advance and check that the number of running anonymous sessions is small before performing the upgrade.
Fixes a bug in the Graph preventing the provisioning process to hang for projects using template in a certain state.
- Knowledge Graph:
visibilityproperty added to the response of the Dataset Details API (#1085)
Fixes a bug in the UI with anonymous sessions that was caught after tagging 0.17.0, but before deploying that version.
- UI New styling of project and datasets (#1984, #2001, #1964, #1978, #2005)
- UI New full-screen session view (#1988, #2009)
- Sessions allow usernames starting with numbers/symbols (#1213)
The way anonymous sessions are handled has changed, and this means that an anonymous session that was started before the upgrade will no longer be accessible afterwards. You may want to notify users in advance and check that the number of running anonymous sessions is small before performing the upgrade.
This release brings improvements and bug fixes to Renku Graph, Renku CLI, Amalthea, Sessions and Renku UI.
- Knowledge Graph: New
GET /knowledge-graph/ontologyproviding documentation for ontology used in KG - Knowledge Graph: Cross-Entity Search resource to filter by namespaces (#1075)
- Knowledge Graph: Dataset Details resource to indicate if Dataset was imported from a tag (#1074)
- Knowledge Graph: A new Project Dataset's Tags API (#1071)
- Knowledge Graph: Link to Dataset's Tags on the Dataset Details and Project's Datasets endpoints (#1072)
- Knowledge Graph: Details about namespaces added to the Cross-Entity Search response (#1070)
- Knowledge Graph: Info about creator's affiliation added to the Project Details response (#1069)
- Knowledge Graph: A new User's Projects resource (#1066)
- Renku CLI: Changed dataset logic to put all files into a dataset's data directory. Allow customizing a dataset's data directory
- UI improve session start flow (#1990, #2003)
- Knowledge Graph: A process to retry all the events failed due to CLI version mismatch
- Renku CLI: Show SSH password prompt when using an SSH key with a password
- UI fix file tree display when changing to original project from fork (#1907, #2015)
- UI prevent repeated queries to projects API (#2017)
- UI render star project button for anon users (#2014)
- UI restore back button navigation on projects for anon users (#2017)
- Knowledge Graph: Renku CLI upgraded to 1.7.1
- Knowledge Graph: Jena upgraded to 4.6.0
This release brings improvements and bug fixes to Renku Graph, Amalthea, Sessions and Renku UI.
- Knowledge Graph: new
GET /knowledge-graph/ontologyproviding documentation for ontology used in KG - Knowledge Graph:
GET /projects/:namespace/:nameto honorAccept: application/ld+jsonheader - Sessions: standardized error responses from the API
- Renku UI: update forms style and layout
- Knowledge Graph: triples store provisioning to support Command Parameters without position
- Amalthea: fixed an issue where some metrics were published more than once
- Amalthea: set sensible values for Prometheus histogram metric buckets
- Sessions: avoid flashing "Failed" status when starting a new session
- Renku UI: show the correct dialog when starting a session from an autosave
- Knowledge Graph: Jena upgraded to 4.5.0
- renku-graph 2.16.0
- renku-graph 2.15.0
- renku-graph 2.14.0
- renku-notebooks 1.10.0
- renku-ui 2.7.0
- amalthea 0.5.2
BREAKING CHANGES! Renku Graph upgrades Jena to 4.5.0 as well as introduces a new Helm chart for Jena. This change requires manual removal of the old Jena StatefulSet. The removal command is:
kubectl delete statefulset <helm-release-name>-jena-master -n <k8s_namespace>
The change also makes the graph.jena.dataset property from the values.yaml obsolete so it can be removed as described in the values changelog file.
This release features improvements and bug fixes to Renku CLI, UI, and User Sessions.
- Knowledge Graph: expose OpenAPI documentation for the lineage endpoint 📃
- Renku CLI: improve UX around renku login when errors occur 👤
- Renku CLI: use existing remote image when starting sessions 💽
- Renku CLI: add an option to skip metadata update when executing workflows 🏃
- Renku UI: add support for Mermaid format in Markdown files 🧜♀️
- Renku UI: update layout, font, and colors 🎨
- Renku UI: add social links 🔌
- User sessions: prevent logging unnecessary errors when starting new sessions ✏️
- Renku CLI: fix merge-tool issues 🧰
- Renku CLI: prevent deleting plans still in use and using already deleted plans 🗑
BREAKING CHANGES! Mind the changes to the structure of the values file for ui and uiserver.
More details available in the values changelog file.
This release updates a minor GitLab version to 14.10.5.
BREAKING CHANGES! We advise admins to make a backup of their GitLab and PostgreSQL volumes before going through this upgrade.
This release updates a minor GitLab version to 14.9.5.
BREAKING CHANGES! We advise admins to make a backup of their GitLab and PostgreSQL volumes before going through this upgrade.
This release introduces important CLI features as well as improvements around dataset upload, user sessions support and knowledge graph.
There are also chart gateway-related updates, we advice admins to please look at the Upgrading section.
- Dataset: improve upload performance and robustness
- Renku CLI: add a command to revert workflows
- Renku CLI: allow exporting datasets to a local directory
- Renku CLI: add support for listing dataset files for a specific dataset version
- Renku Core Service: allow partial updates on dataset and project edit
- Renku Core Service: support chunked file uploads
- User sessions: support for injecting environment variables through the API
- User sessions: support for storing detailed metrics in S3 buckets
- Authentication: improvements in the organization and setup of internal components
- Knowledge Graph: support for project path changes in GitLab
- Dataset: fix intermittent bug in importing datasets
- Knowledge Graph: fixes improving services stability and data correctness
- Renku Core Service: fix project id generation from the project's namespace
- User sessions: fix bug that could lead to endless spinner when autosave information exists
- renku-ui 2.5.0
- renku-python 1.5.0
- renku-notebooks 1.9.0
- amalthea 0.5.0
- renku-gateway 0.14.0
- renku-graph 2.12.0
If using self-signed CA certificates additional values are required when upgrading to 0.13.0 so that the
Traefik Helm chart in renku-gateway can trust these certificates. The values that will need to be added are gateway.traefik.additionalArguments
and gateway.traefik.volumes. Refer to the values file
in the renku-gateway repo for more details.
This release introduces improvements and fixes bugs related to user sessions.
- User sessions: allow specifying files in auto start links
- User sessions: fix a situation where the session start gets stuck in an endless progress spinner
- User sessions: fix handling of S3 buckets that are not hosted on AWS
This release fixes bugs in the user session service.
- User sessions: include information about s3 bucket functionality in the server_options endpoint
- User sessions: improve the parsing of messages from k8s that explain why a session is unschedulable
This release mostly aims to fix the data in the Knowledge Graph. It will start the re-provisioning process which is about wiping out all the data and generating it again.
- Knowledge Graph: fix for the problems where datasets were not present in the Knowledge Graph
- Knowledge Graph: fix for the Lineage REST endpoint to match the API specification
- Knowledge Graph: a new process to speed up provisioning Knowledge Graph with basic project info
- Knowledge Graph: the Cross-Entity search to allow filtering on the creator in a case-insensitive way
This is a minor release that fixes a bug in the renku notebook service that caused existing sessions launched by older renku versions to not be recognized.
- User sessions: successfully list and manage sessions launched by older renku versions
This is a minor release featuring improvements and bug-fixes to Renku CLI, core, graph and UI components.
- Renku Python API: add Activity support in Renku Python API
- Renku CLI: add support to start remote sessions from the CLI
- User sessions: provide better feedback when a session cannot be scheduled due to lack of resources or when initializing a session fails
- Knowledge Graph: add support for identification with ORCID
- Renku UI: prevent errors when working on datasets with images
- Knowledge Graph: fixes of broken data in the Triples Store
A minor bugfix release fixing data problems in the Triples Store.
A minor release adding some features and bug-fixes to the renku components.
The main changes are:
- graph: a new lineage resource to replace current GraphQL endpoint
- graph: cross-entity search resource to allow filtering on since and until
- graph: various fixes related to both corrupted data in Triples Store as well as issues in the Provisioning flow preventing users from finding their data in the Knowledge Graph
- graph: an improvement to the internal processes to detect a lost project re-provisioning event
- graph: other stability improvements
- UI: UX improvements around project and dataset creation
- UI: polish and speedup the logic to start new sessions
- UI: correct bugs affecting the project's dataset page
- UI: improvements to non-logged-in user experience
- renku-python: add Plan and project status support in Renku Python API
- renku-python: add a custom git merge tool for merging renku metadata
- renku-notebooks: switch git proxy sidecar to golang.
More info can be found in release notes of Renku components:
This release does contain potentially breaking changes in renku-notebooks where we previously deprecated securityContext.enabled, but are now setting securityContext directly. Simply delete securityContext and securityContext.enabled from your values.yaml to resolve this.
A minor release adding some features and non-critical bug-fixes to the core service and renku-python CLI.
A release containing new features and bug fixes for CLI, UI and Graph. The main changes are:
- CLI: SHACL validation fixes and improvements
- UI: improvements around starting new sessions
- UI: fixes for projects where the default branch is not called master.
- graph: migration mechanism of the data in the Triples Store
- graph: the Cross-entity search to allow multiple values on type, visibility and creator parameters
More info can be found in release notes of Renku components:
Bugfix release that re-introduces a part of the Renku config that creates auto-saves when sessions crash. This is required only for sessions launched prior to 0.12.6 which still may exist in some deployments. This part of the config will be fully retired in a later subsequent release.
Bugfix release fixing an issue where cloning user repositories was failing during session startup.
Bugfix release fixing an issue where image availability was incorrectly reported if a pinned image was used for interactive sessions.
Minor release with a bugfix for the core service.
Minor release bumping the renku project templates version to 0.3.1.
Includes minor updates to component versions:
Minor release coming with:
- several new features on renku-ui,
- new
/knowledge-graph/entities(cross-entity search) API, - fixes around Cross-Origin Resource Sharing,
- better messaging and reporting on renku-notebooks
- fixes for various bugs in renku-notebooks, renku-ui, renku-gateway and renku-graph services.
More info can be found on release notes of specific components:
- renku-ui 2.1.0
- renku-gateway 0.13.1
- renku-graph 2.4.1
- renku-graph 2.4.0
- renku-graph 2.3.0
- renku-notebooks 1.5.0
Minor release fixing various bugs in renku-python renku-core and graph services. The main fixes are addressing issues in migration and workflow functionality of renku CLI and security and stability bugs in renku-graph.
Please note that the renku-core metrics should be disabled in this release. Recent changes made to Redis are incompatible with the renku-core metrics and cause the whole Renku deployment to not function properly. The renku-core metrics will be fixed in a subsequent release.
More info can be found on release notes of specific components:
Minor release to align Sentry configurations across the components. It includes a few minor bug-fixes.
This is an important upgrade that enables v1.0 of renku-python (renku CLI) to work with the renku web interface, renkulab. The upgrade requires regenerating the metadata in the knowledge graph, which means that for a period of time, searching and accessing datasets and lineage information will be limited and incomplete. The metadata regeneration is done automatically and doesn't require any action from you.
You might be prompted to update your project to the new version of Renku. As a general rule, this update should take less than 30 seconds, and we will provide an estimate of the time required. The update will migrate the metadata for your project and, for most projects, update the base image and the version of the Renku CLI used in interactive sessions. For large projects with thousands of commits or many renku workflows, we recommend doing the migration manually. Please don't hesitate to reach out or open an issue if you encounter problems or are unsure how to proceed.
Most importantly, from this point on, new projects created on renkulab will use renku
CLI >= v1.0. We therefore strongly urge all users to have a look at the myriad of
excellent new features that this major release enables by checking out the
renku-python release notes.
This release completely changes the storage and generation of the knowledge graph metadata,
with vastly improved performance and functionality. We have gone to great lengths to
ensure a smooth transition for older projects and for continuity in the CLI, but
please report issues on discourse or
GitHub.
We hope you like the new features - if you have further questions suggestions for improvements, let us know!
Detailed release notes follow below.
- Support for
renku-python >= 1.0- plugins, workflows, speed 🥳 read all about it! - Improved backwards compatibility for older projects - this means fewer mandatory project updates and interruptions 🎯
- (UI) Streamlined update dialog in project status view 🚀
- (UI) Estimates of project update duration for peace-of-mind 😯
- (UI) improved display of math formulas in markdown preview
- (UI/sessions) more robust autosave infrastructure
- (UI/core) support for project-template-defined parameter validation
- (UI/core) support for icons and description for project templates
- (bug fix) fix problems with dataset "add to project" button
- (UI/sessions) experimental support for cloud storage in user sessions
For full release notes of individual components see:
- UI: https://github.com/SwissDataScienceCenter/renku-ui/releases
- Graph: https://github.com/SwissDataScienceCenter/renku-graph/releases
- CLI: https://github.com/SwissDataScienceCenter/renku-python/releases
- Notebooks: https://github.com/SwissDataScienceCenter/renku-notebooks/releases
BREAKING CHANGES: carefully plan the outage for this upgrade. Because of the underlying changes to the knowledge graph structure, the entire KG has to be rebuilt. Based on our experience, this is orders of magnitude faster than in earlier iterations, but depending on the number of projects it could still take some time. The platform will be usable during this time, but KG features may not fully work (e.g. dataset search)
- (gateway/notebooks) partial support for custom CA certificates
Minor release fixing a bug in the acceptance tests.
Minor release fixing a bug in the Renku template for Keycloak.
This is a minor release featuring improvements to the Renku UI.
- UI: updates to style of alerts, menus, and tables
- User sessions: allow stopping a session that is not fully started (example stopping session)
- User sessions: support links for sharing sessions with additional options (example sharing a link)
Note: this release also updates the version of the keycloak chart to 16.0.4,
but no manual admin action should be needed.
For full release notes see:
This is a major release that includes an important upgrade to GitLab and PostgreSQL components: 14 and 12 major versions respectively.
BREAKING CHANGES
Please follow these instructions carefully.
The resulting changes in the values file should be:
- NEW/EDIT postgresql.persistence.existingClaim will most likely need to be modified in the course of upgrading your PostgreSQL version. See postgres migration instructions
- NEW/EDIT/DELETE gitlab.image.tag might have to be adjusted as we do a GitLab major version bump in with this release.
This is a bugfix release that includes various fixes to user sessions and some improvements to the UI.
- Datasets: allow canceling a search before it completes.
- User sessions: rearrange session menu options.
- User sessions: update Renku commands cheat sheet.
- UI: notify user when a new renkulab version is available.
- File display: highlight code syntax in markdown files.
- File display: support preview of Matlab files.
- File display: add PDF file viewer.
- File display: render LaTeX math.
- User sessions: CPU limit enforcement is now configurable. Admins should refer to the values documentation to configure this in a Renku deployment.
- User sessions: keep auto-saved branches after restoring a session with a newer commit.
- User sessions: a different package is used to decode sessions authorization token.
- Anonymous sessions: not crash anonymous sessions if these are disabled in a deployment.
For a full list of improvements and bug fixes in individual components, please check:
This is a bugfix release that includes various fixes and improvements to user sessions. See renku-notebooks 1.2.0 and amalthea 0.2.1 for more details.
- Chart: Add
tolerations,affinityandnodeSelectorfor user sessions.
- User sessions: checkout the correct alternative branch.
- User sessions: use correct fallback renku image.
- Anonymous sessions: fix failing probes.
This is a bugfix release that contains a fix for launching R sessions with our newest component that manages user sessions (Amalthea). See renku-notebooks 1.1.1 and amalthea 0.1.3 for more details.
Our documentation has been restructured, now articles are reorganized into Tutorials, How-to guides, Topic Guides and Reference (see #2191).
This release includes a new user session controller replacing Jupyterhub. The new controller is not compatible with user sessions created by Jupyterhub, therefore all user sessions need to be terminated prior to upgrading to 0.10.0.
- Documentation: updated documentation on proper teaching etiquette and steps to use renkulab for teaching.
- User sessions: use Amalthea to control sessions through a k8s operator.
- Authentication: log out from GitLab when logging out from Renku.
- Authentication: fix Keycloak token authentication.
For a full list of improvements and bug fixes in individual components, please check:
BREAKING CHANGES!! The admin should plan and warn users ahead of time that their sessions will be terminated when doing the upgrade. The new Loud statuspage component introduced in 0.9.3 can help get the message across.
- The use of Amalthea and removal of Jupyterhub will require some changes. Namely:
- All references to Jupyterhub in the
values.yamlhave been removed and are not required anymore. - Amalthea is installed from a separate helm chart which is now a dependency of therenku-notebookshelm chart. - Several new sections have been added to thevalues.yamlfile which are required by Amalthea. Please refer to the renku values file for more details. - Some older images with Rstudio will open Rstudio in a directory one level above the repository. This can be fixed by upgrading to a newer version of the base image in the Dockerfile in the relevant renku project.
- This version is not backward compatible with the user sessions from older versions. During the deployment the admin should clean up all remaining user sessions and then deploy this version.
- Anonymous sessions do not require a separate namespace and renku-notebooks deployment, if enabled in the values file they now run in the same namespace as regular user sessions.
This is a very minor release that allows messages about maintenance and downtime to be displayed more prominently in the UI. This way the interruptions from upcoming releases can be more effectively communicated to users.
- UI: possibility to make maintenance/downtime notifications more prominently shown. To use this feature, the admin needs to create a new statuspage component called Loud and thick when wanting the message to appear more prominently.
This is a bugfix release that includes various minor fixes: templates and core use a new bugfix CLI version, as well as other fixes for external to SDSC deployments and improved login style.
- Sessions: make enforced limits configurable when using
emptyDirdisk space.
- Templates: Renku and custom templates updated to use Renku
0.16.2(should fix pyshacl and renku conflicting dependencies). - Renku core / CLI: pin pyshacl to version
0.17.0.post1. - Login: make social identity providers style match internal ones.
- UI: configurable welcome page for external deployments.
For a full list of improvements and bug fixes in individual components, please check:
This bugfix release includes fixes to the Knowledge Graph component, see 1.37.2 <https://github.com/SwissDataScienceCenter/renku-graph/releases/tag/1.37.2>__ and 1.37.1 <https://github.com/SwissDataScienceCenter/renku-graph/releases/tag/1.37.1>__.
This release switches to the new UI 🎉 by default. The biggest changes compared to the earlier UI version are explained on the RenkuLab home page and include:
- New aesthetics, look and feel
- Sessions (formerly "interactive environments") shown in the UI within their RenkuLab context
- Issues and Merge Requests shown in the UI within RenkuLab context
- Collaboration: add
Forktab andOpen in Tabbuttons to collaboration pages. - Datasets: support for dataset marquee image in projects
- Sessions: improve functioning and experience of sessions in iframes
- File Browser: allow resizing of file-system navigation view
- Projects: handle primary branches named other than master
- Templates: template updating issue with (see this forum post).
- Renku core / CLI: update rdflib 6 and remove rdflib-jsonld which could not be installed with setuptools
>58.0.2. - CLI: fix renku rm failure in specific cases.
For a full list of improvements and bug fixes in individual components, please check:
Although no special changes are needed in your values file for upgrading to Renku 0.9.0, we want to bring a couple of configurations to your attention:
- To configure and customize the welcome page you have some options, please read the related values file section.
- To enable the new Keycloak renku-theme, you can login to the admin console of
<renku-deployment-url>/auth, go to Realm settings, theme and chooserenku-theme. - The ingress should now include a configuration snippet to support showing sessions in iframes (automatically added by our chart templates).
This is a small release that contains mainly bug fixes to the user sessions and to the UI.
- UI: redesign header to take less vertical space.
- Knowledge Graph: dataset free-text search performance improvements.
- Authentication: enable
renku loginsupport for CLI so that users can interact with private repositories without using a GitLab password or an ssh key.
- Environments: listing orphaned user sessions tied to a deleted project/branch/namespace.
- Environments: bugs with mistyped variable and missing branches in autosave.
- UI: prevent values duplication on session enumerations.
For changes to individual components, please check:
- renku-notebooks: 0.8.18
- renku-gateway: 0.9.5
- renku-ui: 1.0.0-beta5
- renku-graph: 1.36.7
This is just a bugfix release that addresses a problem in the notebook service caused by different naming conventions for user session PVCs.
For changes to individual components, please check:
- renku-notebooks: 0.8.17
This is just a bugfix release that addresses a problem in the notebook service where project names were causing the creation of PVCs in k8s to fail because of characters that k8s does not allow in PVC names (i.e. uppercase letters and underscores).
For changes to individual components, please check:
- renku-notebooks: 0.8.16
This version of Renku introduces the ability to use persistent volumes for user sessions. This is optional and can be enabled in the values file for the helm chart. In addition to enabling this feature users have the ability to select the storage class used by the persistent volumes. We strongly recommend that a storage class with a Delete reclaim policy is used, otherwise persistent volumes from all user sessions will keep accumulating.
Also, unlike previous versions, with 0.8.4 the amount of disk storage will be strongly enforced, regardless of whether persistent volumes are used or not. With persistent volumes users will simply run out of space. However, when persistent volumes are not used, going over the amount of storage that a user has requested when starting their session will result in eviction of the k8s pod that runs the session and termination of the session. Therefore, admins are advised to review and set proper options for disk sizes in the notebooks.serverOptions portion of the values file.
- UI: Add banner advertising new version to logged-in users and various improvements in the new canary deployment itself.
- Environments: Ability to use persistent volumes for user sessions.
- CI/CD: CI action entrypoint typo (3858df0)
- Acceptance Tests: flaky FreeTextDatasetSearchSpec (a872504)
- Acceptance Tests: retry when EOF occurs on the Rest Client (#2211) (e81a212)
- Acceptance Tests: Wait for the dataset search results (#2210) (132ec8b)
- CI/CD: parametrize rancher API endpoint (46a5155)
For changes to individual components, please check:
- renku-ui: 1.0.0-beta4 0.11.14
- renku-notebooks: 0.8.15
When upgrading from 0.8.3 the following steps should be taken based on whether you would like to use persistent volumes for user sessions or not:
Use persistent volumes:
- Edit the notebooks.userSessionPersistentVolumes section of the values.yaml file changing the enabled flag to true and selecting a storage class to be used with every user session. It is strongly recommended to select a storage class with a Delete retention policy to avoid the accumulation of persistent volumes with every session launch.
- Review and modify (if needed) the disk request options in the values.yaml file.
- Review and modify (if needed) the the server defaults in the values.yaml file. These will be used if a specific server options is omitted in the request to create a session and should be compatible with any matching values in the serverOptions section. It also allows an administrator to omit an option from the selection menu that is defined in the serverOptions section and have renku always use the default from the serverDefaults section.
Do not use persistent volumes:
- Review and modify (if needed) the disk request options in the values.yaml file. Please note that if a user consumes more disk space than they requested (or more than what is set in the serverDefaults of the values file) then the user's session will be evicted. This is necessary because if a user consumes a lot of space on the node where their session is scheduled k8s starts to evict user sessions on that node regardless of whether they are using a lot of disk space or not. This sometimes results in the eviction of multiple sessions and not the session that is consuming the most storage resources.
- Review and modify (if needed) the the server defaults in the values.yaml file. These will be used if a specific server options is omitted in the request to create a session and should be compatible with any matching values in the serverOptions section. It also allows an administrator to omit an option from the selection menu that is defined in the serverOptions section and have renku always use the default from the serverDefaults section.
This is a bugfix release that includes fixes to Knowledge Graph. For more details please check the renku-graph 1.36.6 release notes.
This release includes a beta version of the new user interface for Renku. Over the next few releases we will gradually phase out the old user interface. However, for the time being you can use both. Simply switch between the two by clicking the link on the Renku home page.
- chart: configure the Renku realm to use the Renku keycloak theme (d527865), closes #2022
- chart: use keycloak theme with UI 1.0.0 design (35d8980), closes #2022
- docs: new design for renku docs (#2166) (f2f3985)
For changes to individual components, please check:
- renku-graph: 1.36.5
- renku-core and renku-python: v0.16.0
- renku-ui: 0.11.13, 1.0.0-beta3
This is a bugfix release that includes a fix of the link on a project forks in Renku UI.
This release includes a new version for PostgreSQL and GitLab as well as various improvements and bug fixes to Renku CLI and Environments. If your PostgreSQL and/or GitLab were deployed as part of Renku, please make sure to backup your volumes before following the upgrade instructions.
- PostgreSQL and GitLab upgrade: We bump the PostgreSQL version from 9.6 to 11 and the GitLab major version from 11 to 13.
- Project templates: Community contributed template
AiiDAhas been updated. See a06ab24. - Project templates: Project templates come with Renku CLI
v0.15.2by default. - Renku CLI: add support to dataset update for detecting changes to local files.
- Renku CLI: add support to export OLOS datasets.
- Renku CLI: add JSON output format to
renku dataset lsandrenku dataset ls-files. - Renku CLI: detect filename from content-disposition header when adding a dataset.
- Environments: remove storage options when launching environments if PVC feature is not enabled.
- Project templates: fix project creation to use pinned Renku CLI version.
For changes to individual components, please check:
BREAKING CHANGES
Please follow [these instructions](https://github.com/SwissDataScienceCenter/renku/tree/master/helm-chart#upgrading-to-080) carefully.
The resulting changes in the values file should be: * NEW/EDIT postgresql.persistence.existingClaim will most likely need to be modified in the course of upgrading your PostgreSQL version. See [these instructions](https://github.com/SwissDataScienceCenter/renku/tree/master/helm-chart/utils/postgres_migrations/version_upgrades/README.md) * NEW/EDIT/DELETE gitlab.image.tag might have to be adjusted as we do a GitLab major version bump in with this release.
- Knowledge Graph: improve lineage visualization by skipping overridden edges
- Knowledge Graph: fix rest client to classify failure responses properly
For more details please check renku-graph 1.36.3
A new client application renku-cli in keycloak has been added. This needs a value for global.gateway.cliClientSecret which could be generated through openssl rand -hex 32.
- Notebooks API: enable endpoint for getting autosave information
- Notebooks: missing annotation handling in marshmallow
- Renku CLI: support moving files between datasets with
renku mv(CLI documentation). - Renku CLI: ability to update local project from its template and to update the Dockerfile to install the current version of renku-python using renku migrate.
- Projects: ability to generate project-creation links, embedding metadata to automatically pre-fill input fields. For more details on how to use this feature please read our documentation.
- Renku CLI: support for Unicode paths in renku run (including emojis).
- Projects: add preview for common hidden files.
- Templates: use Renku CLI 0.14.2
- Environments: If Automatically fetch LFS data enabled, unset LFS auth mode in init container
- Projects: restore support for project-level default environments parameters (e.g. CPU and memory requests).
- Core service: fix project_clone with git ref specified.
- Knowledge graph: event status update process to remove delivery info in a single transaction
- Knowledge graph: improvements in lost subscriber node finding algorithm
For changes to individual components, please check:
- renku-ui: 0.11.11, 0.11.10
- renku-notebooks: 0.8.11
- renku-python: v0.14.2
- renku-graph: 1.36.2, 1.36.1
- Docker images: a new base-image extension is added that includes a full desktop server, which allows users to run Linux desktop applications directly from their RenkuLab sessions. For more information please refer to this discourse post
- Projects: improve UX when forking a project, and handle up to 1000 namespaces
- Projects: allow setting project avatar
- Environments: simplify getting the registry image URL for running sessions
- Docker images: update all of the base libraries and change the underlying operating system to Ubuntu 20.04 as well as upgrades the python version to 3.8.
- Templates: bump Bioconductor version to 3.12
- Templates: bump R version to 4.0.4
- Templates: use Renku CLI 0.14.1 and above mentioned docker images
- Knowledge graph: new service used for routing commits synchronization
- Collaboration: fix issue page not loading properly
For changes to individual components, please check:
- Core: add error handling if push from temporary branch fails
- Core: fix handling of '@' in filenames
- Core: fix save and push to correctly handle merge conflicts
- Service: sync service cache with remote before operations to prevent cache getting out of sync
- Datasets: allow importing a dataset from a non-public project
- Graph: fix fail to update event status when triples generation fails
- Deployment: fix gateway gitlabClientSecret in minimal-values template
- Datasets: show a notification when uploading big files
- Datasets: improve naming for imported datasets
- Datasets: sort by date on the free-text dataset search
- Projects: update the project fork flow to match project creation
- CLI: add service component management commands
- Datasets: the dataset details returns information about project it belongs to
- Lineage: prevent showing the whole graph when displaying a single file's lineage
- Lineage: support for committers name changing
- Knowledge Graph: improve provisioning flow; re-process stale events sooner, use smaller processes
- Core: exclude renku metadata from being added to git lfs
- Datasets: fix creation date when searching datasets
- Datasets: fail gracefully when trying to access a missing dataset
- Datasets: dataset import to move temporary files and become more resilient to errors
- Datasets: handle datasets with ',' in the name correctly
- Environments: image pull secret for pod restart
- Environments: support for long project title
- User interface: check lfs status properly when previewing a file
- User interface: fix broken markdown preview caused by links without a reference
- User interface: handle sub-groups on projects list
- Core: call git commands for batches of files to prevent hitting argument length limits
- Core Service: correctly handle HTTP server errors and ref on project.clone
- Core Service: use project_id as part of project filesystem path
For changes to individual components, please check:
Breaking change Keycloak chart dependency has been upgraded from 4.10.2 to 9.8.1 which will trigger an irreversible database migration, check out the upgrade instructions for more details.
Most notably, keycloak values are less nested, so at the level of the Renku chart values, keycloak.keycloak.X.Y becomes keycloak.X.Y. You can also check out the instructions on how to upgrade aspects not covered by default in the Renku chart.
If the Renkulab deployment includes keycloak, the values file should be modified as follows: * DELETE - the section keycloak.keycloak.persistence has been removed. Database connection details are specified through the keycloak.extraEnv and keycloak.extraEnvFrom blocks. See the Renku values file for reference. * EDIT - keycloak.keycloak.username has been moved to global.keycloak.user.
Finally, before applying the helm upgrade, the Keycloak statefulset should be deleted.
- User interface Improve UX for non-logged users (0.11.5)
- User interactive sessions Some bug fixes (0.8.9)
- Knowledge graph Bug fixes and small improvements (1.27.3 to 1.27.5).
- Deployment Helm tests enabled to run our acceptance tests suite (see the acceptance tests section of our deployment documentation). A make-values.sh script is available to generate a minimal values file for Proof-of-Concept deployments, for more information please refer to our deployment documentation.
This is a bugfix release, it contains fixes for the Knowledge Graph (PRs #608 and #609) and user interactive sessions (renku-notebooks 0.8.8).
- Dataset show Dataset metadata can now also be seen in the Renku CLI using the
renku dataset showcommand. - Knowledge graph Access control to resources on knowledge graph.
- RenkuLab Support for deployments which use TLS certificates issued by a private CA.
- UI Improve performance of file preview
- UI Show project datasets even if user is not logged in
- Interactive sessions Fix a bug that made the automatic pull of LFS data on session start fail for private repositories.
- Interactive sessions Improve handling of failed session launches.
- Interactive sessions Fix status information on session termination.
- Project migration Feedback and speed of the recently introduced migration for workflows has been improved to handle very large projects better.
For changes to individual components, check:
This is a patch release that includes a notebooks change and some improvements to the Knowledge Graph.
This release contains some very nice improvements to the file and datasets management and visualization as well as project migrations.
- Dataset removal A dataset can be now removed from a project, either from the UI or with the Renku CLI.
- Pinned environments image A project can pin interactive environments to a specific image, independent of the content of the project. This can be useful for situations like courses where everyone should use the environment defined by the instructor. To take advantage, see the renku configuration file documentation.
- Project migration Project migration has been improved, allowing users to migrate the template, Dockerfile and Renku version with just one click. Information about the latest and current Renku CLI and template versions are displayed in the Status section of a project. Additionally, a migrationscheck command is available in Renku CLI.
- Dataset upload When uploading files, a progress bar is displayed.
- Dataset visualization For a better experience on dataset listing inside projects, description and author list have been cropped. The full content of both is still available when accessing the dataset.
- File preview Preview of C++ and Fortran files is supported.
- File download Files can be downloaded from the Renku UI.
- Autosaved work Commits with autosaved content are marked with
*and dialog is more specific. - Autosave git LFS When a session is closed and work is automatically saved, large files are added to LFS according to the project's settings see renku config documentation.
- Core Renku CLI commit messages are shortened to 100 characters for readability.
- New projects Templates to create new projects now use the new Renku CLI version
0.12.2by default.
- Auth credentials: the way Renku environments handle git credentials has been improved.
For changes to individual components, check:
- No changes required in the values file for this upgrade
This release brings several smaller improvements and bug-fixes, the most notable of which are:
- Datasets Add new fields and the possibility to edit existing fields to the web UI.
- Knowledge Graph Improve information flow related to KG integration and Renku version updates in the UI.
- Project creation: improve name validation, the handling of non ASCII characters and a bug which led to failures when fetching the available templates.
- Graph processing: fix a bug in prioritizing events for processing.
For details check out the individual component updates.
This release features an update to the default project templates, bumping the default renku CLI version to ``0.12.0` <https://github.com/SwissDataScienceCenter/renku-python/releases/tag/v0.12.0>`_ and some backend bug fixes.
- Graph building: several improvements to graph building, including a fix for metadata compaction in renku-core that caused some entities to not get processed.
This release brings a lot of important new features to both Renkulab and the Renku CLI. It's our best one yet!
- Project templates: you can now create custom templates for your projects and use them on project initialization. Great for groups or courses! See the docs for more details.
- Datasets: you can now search for datasets and import them into projects directly from the Renkulab web UI. The dataset import and creation flow has also been much improved thanks to changes in the core service backend. Note that importing datasets from other renku projects from the UI currently works only for datasets in public repositories.
- Data import: files can be imported into datasets directly from a URL.
- Project migration: the metadata of renku projects occasionally changes. In order for all the components to work well together, the metadata must be kept in sync. Previously you needed to do this manually with the CLI but now it's as easy as clicking a button.
- Template simplification: We have decoupled the CLI version from the base image and made it easier to override in your own environments. See the project template README for details.
- Improved editor: All text editing components are using an enhanced editor that allows seamless switching between WYSIWYG and markdown.
- renku save: the Renku CLI now features a
savecommand that simplifies the process of committing and pushing your project to the server.
- Dataset deletion: Datasets used to stick around even after getting deleted from the project. This has now been fixed and deleted datasets no longer appear in the dataset listings.
- git credentials: the interactive sessions now handle your git credentials in a way that allows you to seamlessly access any of your private repositories on renkulab from within an interactive session.
- git hooks in interactive sessions: git hooks were not previously installed per default in interactive sessions, which meant that some nice features like automatically pushing large files to LFS did not work correctly. This has now been corrected and should hopefully save many repositories from improperly handled data!
- graph redesign: Under the hood, the renku-python library has a completely redesigned knowledge graph model. This enormous effort doesn't translate to user-visible improvements yet, but they're coming in the next release!
Many other improvements and bug fixes across all of the renku components, which have significantly improved the stability of the entire platform!
To upgrade your existing renkulab project to the latest images, the easiest is
if you copy/paste a Dockerfile that suits your project
(python/R/Bioconductor) from the renku project templates repository.
Note that even if you upgrade the image, the project in the repository will still
need to be migrated. You can do this on the command line by running renku
migrate in your project or follow the instructions in the UI when prompted.
- Breaking change: Postgresql chart: we have switched to the Bitnami version
of the Postgresql
helm chart - this requires a manual intervention when upgrading from renku
0.6.8. - Kubernetes: renku is now compatible with kubernetes >= 1.16 (tested on 1.16)
- Helm3: the renku helm charts are now compatible with helm 3
This is a minor release that contains improvements and fixes to the UI.
⭐️ support for air-gapped deployments: RenkuLab's UI contains all resources necessary to run (no connection to the internet needed).
⭐️ integration with statuspage.io: users get a visual notification for incidents and scheduled maintenance, additionally they can check the status of RenkuLab's components in <renkulab>/help/status.
🚄 anonymous users: can navigate in public projects' collaboration tab
🚄 privacy: add privacy page and cookie consent banner
🚄 markdown: display of relative paths, and improvement in file preview
🚄 Julia: source and project files correctly rendered in the file browser
🐛 500 error code is handled at the UI when starting environments
🐛 fix rendering issues with WYSIWYG editor toolbar
- The version in the welcome page can be updated at
ui.welcomePage.textin the values file. - The integration with statuspage.io can be enabled by adding the unique project ID at
ui.statuspage.idin the values file
This is a bugfix release.
🐛 fix pulling of lfs data in the init container of interactive environments
- The version in the welcome page can be updated at
ui.welcomePage.textin the values file.
This is a release that improves the way images for private projects get pulled, no more GitLab sudo token needed!
- use user credentials for pulling images for private projects
- user oauth token is removed from repository URL
- kubernetes versions < 1.14 are not supported anymore
- The version in the welcome page can be updated at
ui.welcomePage.textin the values file.
This is a release which only updates the version of the gitlab chart dependency.
- More flexibility in configuring the gitlab instance through the values file.
- No new values required, a gitlab.extraConfig block can be used to add settings to the gitlab.rb configuration file.
This is primarily a bugfix release.
- Fixes a bug which prevented the selection of a non-master branch when launching an environment.
- Improved display of merge requests in the UI
For changes to individual components, check:
- renku-ui 0.10.3
- No new values required in the values file
- The version in the welcome page can be updated at ui.welcomePage.text
⭐️ Project details now include a listing of the commit history
🚄 Environments: auto-saved branches are filtered per username
🚄 Improve markdown rendering and code highlighting
🚄 Editing markdown files is easier as ckeditor is partially integrated inside Renku
- Dataset contains all folders from unzipped file
- Failing to retrieve metadata for one dataset does not cause the others to fail
- Improved UX for when datasets take too long
- Datasets: no failure when adding ignored files
- The default R template now uses the latest R (4.0.0). To update it in an existing R project, replace the first line in the Dockerfile with
FROM renku/renkulab-r:4.0.0-renku0.10.4-0.6.3 - A Bioconductor image with bioc 3_11 is now available. To use it replace the first line in the Dockerfile with
FROM renku/renkulab-bioc:RELEASE_3_11-renku0.10.4-0.6.3 - Docker images in project templates use
renku0.10.4
GitLab version: the Renku chart now installs GitLab >= 12.9.0 by default.
GitLab versions < 12.7.0 are supported too, but a .gateway.oldGitLabLogout: true has to be set explicitly. Note that GitLab versions where 12.7.0 <= version < 12.9.0 are not supported.
For changes to individual components, check:
- renku-ui 0.10.2
- renku-python 0.10.4
- renku-gateway 0.8.0
- renku-notebooks 0.7.4
- renku-graph 1.0.3 to 0.55.4
- No new values required in the values file
- The version in the welcome page can be updated at ui.welcomePage.text
⭐️ Environments: logged-in users without developer access can launch interactive sessions from a project.
- ⭐️ Environments: interactive sessions can be enabled for logged-out users. Please see the
- documentation for details.
⭐️ Hiding/showing code cells is now possible from the UI
🚄 Datasets: dataset creation and import unified in the UI
- Datasets now include the folder hierarchy in file listings
- Datasets: avoid recursive addition of the data directory in Renku CLI
- Datasets: fix export to Dataverse
- Datasets: fix metadata commit after renku dataset unlink
- Environments: improve styling
- A maintenance page can now be displayed for when Renkulab is undergoing a scheduled maintenance 🔧
- Help page and dropdown contain links to Renku and Renku CLI documentation 📖
- Easy UI access to GitLab projects, user settings and user profile 👤
- Python environments now include a plugin to monitor memory usage visually 📈
- A new Renku docker image with Julia is now available. 📣 To use it just replace the first line of your Dockerfile with
FROM renku/renkulab:renku0.10.3-julia1.3.1-0.6.2 - The Tensorflow Renku docker image with Cuda and Tensorflow 1.14 is now available with the latest Renku
0.10.3. To use it just replace the first line of your Dockerfile withFROM renku/renkulab:renku0.10.3-cuda10.0-tf1.14-0.6.2 - Docker images in project templates use Renku 0.10.3
For changes to individual components, check:
- If you want to enable interactive sessions for anonymous users, see the values changelog file and anonymous sessions documentation
- The version in the welcome page can be updated at ui.welcomePage.text
Released 2020-04-01
⭐️ Datasets can be imported from data repositories through the UI
⭐️ Datasets allow uploading file hierarchies in zip format
⭐️ CLI: Datasets metadata is editable. Please see the Dataset documentation for details.
⭐️ CLI: enable importing renku datasets
⭐️ CLI: Enable working with data external to the repository #974
🚄 A file upload can be canceled when creating a dataset
🚄 Environments tab displays information about the resources requested
🚄 Environments tab provides an easy access to the branch/commit file listing
🚄 Improvements to the handling of markdown content
🚄 CLI: starting this version a new migration mechanism is in place, renku command will insist on migrating metadata if its outdated.
- Various improvements on markdown display for collaboration
- Make help channels more visible
- CLI: wildcard support when adding data from git
- Docker images and project templates use Renku 0.10.2
- A new minimal Renku project template is available on project creation! Use this template if you're using a language other than R or python, or if you're renku-izing an existing python project.
- Newer renkulab docker images also provide interactive environments with a nicer shell (powerline).
- Datasets now show file listing with folder hierarchy
- Search uses clearer labeling
- Various fixes to dataset command line bugs
For changes to individual components, check:
- renku-ui 0.9.1 and 0.9.0
- renku-python 0.10.0
- renku-notebooks 0.7.1
- renku-graph 0.55.4 to 0.49.0
- No new values required in the values file
- The version in the welcome page can be updated at ui.welcomePage.text
Released 2020-03-06
This release includes exciting new features and provides an improved user experience, mostly with respect to dataset handling.
⭐️ Datasets can be created from the UI
⭐️ Files can be added to a dataset from the UI
⭐️ Datasets can now be exported to Dataverse
🚄 Support project-level default settings for environments
🚄 Relevant project/namespace information is shown at
/projects/user-groupname/ path
🚄 Cleanup error messages for Renku CLI usage
🚄 Dataset importing is faster with Renku CLI
🚄 Restructured our documentation
- R-markdown
rmdfiles can be visualized within Renkulab ✔️ - Group avatars are displayed 👤
- Improved presentation for merge request and issues
- A Gitlab IDE link has been made available for working with Renku projects
- Link to see a project’s fork information
- Docker images and project templates now use Renku 0.9.1
- A Renku docker image with Bioconductor is now available 📣
- R projects now have the directory structures fixed
- Python now comes with powerline to simplify the command line prompt
- JupyterHub has been updated to version 1.1.0
- Prometheus metrics available for graph services
- LFS data is now retrieved when the checkbox is selected 🐞
- Close the fork dialog after forking
- Various fixes for lineage including performance
For changes to individual components, check:
- renku-ui: 0.7.3 and 0.8.0
- renku-gateway 0.7.0
- renku-python 0.9.0 and 0.9.1
- renku-graph 0.48.0
- renku-notebooks 0.6.2
- No changes required in the values file for this upgrade
Released 2019-12-04
This is a bugfix release that updates the GitLab version required to allow changing the project name when forking (see #616 and #626).
Released 2019-11-27
⭐️ Datasets are now displayed inside a Renku project
⭐️ Datasets can now be searched within available Renku projects
- Changed project URLs to show namespace and name instead of project ID
- Reworked collaboration view with issues list and collapsing issue pane 👥
- Enabled search by username and group 🔍
- Fork functionality now allows changing the name 🍴
- Better tools to get information about interactive environments 🕹
- Better consistency with project and interactive environment URLs 🎯
- Commit time is local timezone aware 🕖
- Images and project templates now use Renku 0.8.2
- A Renku docker image with CUDA, Tensorflow and Tensorboard is now available 📣
- User profile redirects to Keycloak profile 👤
- Simplified deployment with automatic secrets generation ✔️
For changes to individual components, check:
- renku-ui 0.7.2, 0.7.1, 0.7.0 and 0.6.4
- renku-gateway 0.6.0
- renku-python 0.8.2, 0.8.1, 0.8.0, 0.7.2 and 0.7.1
- renku-graph 0.29.3
- renku-notebooks 0.6.2, 0.6.1 and 0.6.0
- Lineage visualization bugs addressed 🐞
- Users with developer permissions can now start an interactive environment 🚀
- Update values file according to the values changelog
Released 2019-10-30
This is a bugfix release that fixes a SPARQL query in the graph service which was causing Jena to stall and run out of memory (See #159 and #163).
Released 2019-08-28
This is a relatively minor update.
- ⭐️ on launching an interactive environment, the user is shown the status of the
- image build - no more guessing whether the Docker image is there!
- ⭐️ the source of project templates is now configurable so a platform admin can
- provide custom templates if needed
⭐️ data and code nodes are styled differently in the graph view
- ⭐️ the base user images have been updated, notably the R image is now based on
- Rocker instead of conda
For individual component changes:
- renku-notebooks version 0.5.1
- renku ui: version 0.6.3 and PRs 576 and 578