Version 0.9.0

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

Improvements

• Collaboration: add Fork tab and Open in Tab buttons 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.

Bug Fixes

• 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.
• GitLab charts: fix registry ingress.

Individual components

For a full list of improvements and bug fixes in individual components, please check:

• renku-ui: 1.0.0.

• renku-core: 0.16.1.

• renku-graph: 1.37.0.

Upgrading from 0.8.7

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 choose renku-theme.
• The ingress should now include a configuration snippet to support showing sessions in iframes (automatically added by our chart templates).

Version 0.8.7

This is a small release that contains mainly bug fixes to the user sessions and to the UI.

Improvements

• UI: redesign header to take less vertical space.
• Knowledge Graph: dataset free-text search performance improvements.
• Authentication: enable renku login support for CLI so that users can interact with private repositories without using a GitLab password or an ssh key.

Bug Fixes

• 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.

Individual components

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

Version 0.8.6

This is just a bugfix release that addresses a problem in the notebook service caused by different naming conventions for user session PVCs.

Individual components

For changes to individual components, please check:

• renku-notebooks: 0.8.17

Version 0.8.5

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

Individual components

For changes to individual components, please check:

• renku-notebooks: 0.8.16

Version 0.8.4

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.

Improvements

• UI: Add banner advertising new version to logged-in users and various improvements in the new canary deployment itself.
• Notbooks: Ability to use persistent volumes for user sessions.

Bug Fixes

• 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)

Features

• CI/CD: parametrize rancher API endpoint (46a5155)

Individual components

For changes to individual components, please check:

• renku-ui: 1.0.0-beta4, 0.11.14
• renku-notebooks: 0.8.15

Upgrading from 0.8.3

When upgrading from 0.8.3 the following steps should be taken based on whether you:

Use persistent volumes:

1. 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.
2. Review and modify (if needed) the disk request options in the values.yaml file.
3. 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:

1. 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.
2. 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.

Version 0.8.3

This is a bugfix release that includes fixes to Knowledge Graph. For more details please check the renku-graph 1.36.6 release notes.

Version 0.8.2

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.

Improvements:

• Core Service: add group and remove subcommand to graph workflow
• Core Service: add renku version as a project template parameter
• CLI: login to git from CLI
• Core Service: include parameter values in provenance
• Knowledge Graph: marking deleted commit event as awaiting deletion events and securing GraphQL endpoint
• UI: new design

Bug Fixes

• tests: CSS for the Login button on the provider page (#2178) (d1a0149)

Features

• chart: configure the Renku realm to use the Renku keycloak theme (#2022) (d527865)
• chart: use keycloak theme with UI 1.0.0 design (#2022) (35d8980)
• docs: new design for renku docs (#2166) (f2f3985)

Individual components

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

Version 0.8.1

This is a bugfix release that includes a fix of the link on a project forks in Renku UI.

Version 0.8.0

This release includes breaking changes: 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.

Improvements

• 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 AiiDA has been updated. See a06ab24.
• Project templates: Project templates come with Renku CLI v0.15.2 by 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 ls and renku dataset ls-files.
• Renku CLI: detect filename from content-disposition header when adding a dataset.

Bug Fixes

• Environments: remove storage options when launching environments if PVC feature is not enabled.
• Project templates: fix project creation to use pinned Renku CLI version.

Individual components

For changes to individual components, please check:

• renku-notebooks: 0.8.12
• renku-python: v0.15.1, v0.15.0.

Upgrading from 0.7.13

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 these instructions.
• NEW/EDIT/DELETE gitlab.image.tag might have to be adjusted as we do a GitLab major version bump in with this release.

Version 0.7.13

Bug Fixes

• 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 release 1.36.3

Upgrading from 0.7.12

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.