Releases: SwissDataScienceCenter/renku
0.63.0
This release introduces copying projects. This feature makes it easy for course instructors to distribute course
materials to students.
User-Facing Changes
🌟 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).
Individual Components
0.62.1
Renku 0.62.1 fixes a bug that prevented users to launch sessions with
user secrets in Renku 1.0.
User-Facing Changes
🐞 Bug Fixes
- Data services: Correctly map user secrets in Renku 1.0 sessions
to use the provided filename.
Individual components
0.62.0
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.
User-Facing Changes
🌟 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).
Internal Changes
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
Individual Components
0.61.2
Renku 0.61.2 fixes a bug that prevented users from resuming Renku V2 sessions after they have been hibernated because they were idle.
User-Facing Changes
🐞 Bug Fixes
- Sessions: Correctly resume hibernated sessions.
Individual components
0.61.1
Renku 0.61.1 introduces a few bug fixes for the previous release.
User-Facing Changes
🐞 Bug Fixes
- Sessions: Correctly launch sessions that request dedicated resources classes
Internal Changes
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
Individual components
0.61.0
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]{.title-ref} 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.
User-Facing Changes
✨ 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.
Internal Changes
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
Individual Components
0.60.0
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.
User-Facing Changes
✨ 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).
Internal Changes
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.
Individual Components
0.59.2
Renku 0.59.2 is a bugfix release that fixes a bug in Renku 2.0 where project editors could not edit project information.
User-Facing Changes
🐞 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).
Internal Changes
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).
Individual Components
0.59.1
0.59.0
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.
User-Facing Changes
🌟 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).
Internal Changes
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.