Releases: SwissDataScienceCenter/renku
0.45.1
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.
Internal Changes
🐞 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)
Individual components
0.45.0
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.
User-Facing Changes
✨ 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).
Internal Changes
✨ 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
slug
andname
and notitle
property (#1741). - KG: Clean up process removing project tokens close to their expiration date (#1812).
Individual components
0.44.0
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.
User-Facing Changes
🌟 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
getSessions
query 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).
Internal Changes
Improvements
- Data services: New API endpoints to store and retrieve user preferences have been added to support the projects pins (#85).
Individual components
0.43.0
Renku 0.43.0
brings improvements to the KG API and 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
.
User-Facing Changes
✨ 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/version
API. (#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.
Internal Changes
Improvements
- KG: KG services to work with both
Base64
encoded 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
Individual Components
0.42.1
Renku 0.42.1
is a bugfix release that addresses the following bugs in a few services:
- creating new resources in the
data-services
API - 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-services
into user sessions
Individual components
0.41.1
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.
Individual components
0.42.0
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]{.title-ref} 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.
User-Facing Changes
🌟 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).
Internal Changes
renku-gateway
can now proxy to Keycloak endpoints.
Individual components
0.41.0
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.
In addition, 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.
User-Facing Changes
🌟 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).
Internal Changes
This release is a breaking change to the Helm values file and it requires minor edits to the following field:
ui.homepage
removed the unusedprojects
field and added theshowcase
field.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
crc
field in the values file has been renamed todataService
, all child fields remain the same functionally and by name. - the
global.gitlab.url
value should be filled in with the Gitlab URL
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-notebooks
now get S3 cloud storage configuration fromrenku-data-services
renku-gateway
now 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
Individual components
0.40.2
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
Individual components
0.40.1
Renku 0.40.1
reverts recent changes to Lucene configuration in the Triples Store preventing users from searching by keywords.
User-Facing Changes
🐞 Bug Fixes
- KG: Use the
StandardTokenizer
to allow searching by keywords containing underscore signs.