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 unused projects field and added the showcase 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 to dataService, 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 from renku-data-services
• renku-gateway now provides credentials for the cloud storage potion of renku-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

• 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

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

• renku-data-services v0.0.3

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.

Individual components

• renku-graph 2.43.1

0.40.0

Renku 0.40.0 introduces UI performance improvements and fixes internal KG and Triples Store performance issues.

User-Facing Changes

✨ Improvements

• 🚀 UI: Reduce the compiled bundle size to improve performance of the UI (SwissDataScienceCenter/renku-ui#2818, SwissDataScienceCenter/renku-ui#2827, SwissDataScienceCenter/renku-ui#2832)
• 🚀 UI: [Dashboard] Speed up showing the warning for non-indexed projects (SwissDataScienceCenter/renku-ui#2824)
• 🛠️ UI: [Projects] Use the KG API to update a project's metadata for the following cases: visibility, keywords and description (SwissDataScienceCenter/renku-ui#2793)

Internal Changes

🐞 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 (SwissDataScienceCenter/renku-ui#2831)

Individual components

• renku-graph 2.43.0
• renku-ui 3.13.1

0.39.3

Renku 0.39.3 fixes various bugs.

Internal Changes

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

0.39.2

Renku 0.39.2 fixes a bug when pausing sessions.

🐞 Bug Fixes

• Renku Notebooks: fix a bug in session hibernation (#1645)

Individual components

• renku-notebooks 1.19.1

0.39.1

Renku 0.39.1 fixes bugs in the Helm chart introduced by 0.39.0.

Internal Changes

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.

0.39.0

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.3 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 to jena.*
• notebooks.amalthea.* moved to amalthea.*
• notebooks.dlf-chart.* moved to dlf-chart.*

For more details please refer to the explanation in helm-chart/values.yaml.changelog.md.

Internal Changes

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.

0.38.0

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.

User-Facing Changes

✨ 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).

0.37.0

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.

User-Facing Changes

🌟 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).

Internal Changes

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.idleThresholdSeconds in the values file was renamed to notebooks.culling.idleSecondsThreshold.

Individual components

• amalthea 0.9.1
• renku-notebooks 1.19.0
• renku-ui 3.13.0