2.11.0

Renku 2.11.0 has many new improvements, most notable of these are support for arm image builds, improved status reporting for code repositories and integrations, and support for Gtilab redirects. Please read on for more details. Platform administrators upgrading Renku to this release should also check out the changes in the dedicated section - some of which may require additional actions depending on your setup and configuration.

User-Facing Changes

🌟 New Features

• ⏩ UI: interrupt the session start flow and show feedback when repositories aren’t accessible
• UI: Support for building arm64 images.

✨ Improvements

• 👩‍💻 UI: improve how repository permissions are shown on the project page
• 👥 UI: show group role descriptions when adding/editing group members
• 🖍️ UI: streamline form appearance
• 🚫 UI: show a concise message when reaching no longer supported Legacy pages

🐞 Bug Fixes

• Backend: fix a concurrency issue with token refreshes for integrations.

Internal Changes

Improvements

• Backend: indicate supported platforms when checking a session image
• Backend: revamp group role permissions to match users expectations
• Keycloak: Upgrade Helm chart and version
• Gateway: Support for Gitlab redirects.
• UI: Add Prometheus metrics for the NodeJS server
• Backend: Add Sentry to the K8s watcher

Bug Fixes

• Helm: add environment variable for NodeJS self-signed CA certificates

Notes for Renku Administrators

A few notable changes:

• The Helm chart flag that controls whether legacy (v1) services are deployed (enableV1Services) has been changed so that starting with this release its default value is false. That means that if you do not take action and you are using the default value from before all v1 services will be shutdown with this release. If you wish to keep running v1 services you can change this flag to true in your values file. However, please note that with the next Renku release 2.12.0, this flag will be fully removed and along with it all v1 services.

• The Helm chart for Keycloak has been updated. This results in an upgrade of the version of Keycloak from 20.0.1 to 21.1.1. You can compare the changes in the helm chart on the Gtihub repository. Depending on your values file there may be more changes than just the change in the Keycloak image version. In our tests for a simple configuration we did not encounter any problems. But it is better to compare the helm charts and be aware of the changes for your specific case when before you apply the upgrade. The Keycloak upgrading guide is also a useful resource you should consult before performing the upgrade. In addition, it is always a good practice to backup your data before such an upgrade.

• If you are using the “build environments from code” feature, then you should apply the new build strategy (renku-buildpacks-v3) from the Renku data services repository. This should be applied (via kubectl apply -f <filename>) in the same namespace where Renku is deployed.

• We have added a platform property on all resource pools, this defaults to linux/amd64. So if you have any resource pools that are using arm64 you need to patch these manually using the swagger page after you upgrade Renku. For example, on renkulab.io we have the following resource pools that run on arm64.

  {
    "id": 74,
    "name": "CSCS - Daint - Debug"
  }
  {
    "id": 75,
    "name": "CSCS - Daint - Normal"
  }
  {
    "id": 76,
    "name": "CSCS - Clariden - Debug"
  }
  {
    "id": 77,
    "name": "CSCS - Clariden - Normal"
  }
  {
    "id": 85,
    "name": "CSCS - Santis - Debug"
  }
  {
    "id": 86,
    "name": "CSCS - Santis - Normal"
  }

  Using the id, one can send a patch request for each resource pool through the swagger page with the following payload so that the platfrom property is updated.

  { "platform": "linux/arm64" }

• Additional changes are required in the Helm chart values file so that builds for arm resource pools can happen on arm nodes. You can see an example of these values in the Renku helm chart. These will configure the builder and run images to use for arm , as well as the node selector terms and tolerations so that the image builds actually occur on arm nodes. Note that cross-platform builds do not work due to limitations with buildpacks and CUDA.

Individual components

• renku-data-services v0.61.0
• renku-data-services v0.62.0
• renku-ui v4.12.0
• renku-ui v4.13.0
• renku-gateway 1.8.0

2.10.3

Renku 2.10.3 fixes a bug with sending metrics to Posthog. If your Renku deployment is not setup to send metrics to Posthog then this will have no effect. This will temporarily disable sending metrics to Posthog about users who register or update their profiles. The functionality will be enabled again in an upcoming release.

Internal Changes

Bug Fixes

• Data service: do not send any identify events for users to Posthog

Individual components

• renku-data-services v0.60.5

2.10.2

Renku 2.10.2 fixes a but with patching user sessions.

User-Facing Changes

🐞 Bug Fixes

• Sessions: fix an issue with changing the resource class of a hibernated session that results in the removal of node affinities

Individual components

• renku-data-services v0.60.4

2.10.1

Renku 2.10.1 introduces several bug fixes several issues related to sessions, data connectors and the group search page.

User-Facing Changes

🐞 Bug Fixes

• Sessions: fix an issue where resuming a session using a private container image would not work if the session was paused for more than a few hours
• Data Connectors: fix the warning shown on writable data connectors
• Session: allow args and command to be reset when editing a session environment based on an external image
• Admin: fix and restyle admin page components

Internal Changes

Bug Fixes

• Sessions: fix an issue with using private container images from the internal GitLab
• Data Connectors: fix an issue when using % in WebDav URLs
• K8s watcher: add Sentry configuration
• API: fix API spec for patching session environments
• Search: fix searching data connectors in a group
• Data Connectors: set “host” as a non-sensitive field
• Data Connectors: fix issue when moving parent project to another namespace
• Search: fix search index not up to date when a group or a project is deleted
• Data Connectors: fix issue with default values for Polybox and SwitchDrive
• Projects: copy secret slots when a project is copied
• Sessions: fix labels and annotations not being reset when changing resource classes
• UI: add prometheus metrics to UI

Individual components

• renku-data-services v0.60.1
• renku-data-services v0.60.2
• renku-data-services v0.60.3
• renku-ui v4.11.1

2.10.0

Renku 2.10.0 introduces a host of improvements to Renku: container images are checked when creating external session environments, data connectors with credentials can be properly skipped at session launch and users are warned when creating data connectors with insecure permissions among other improvements and fixes.

User-Facing Changes

✨ Improvements

• 📦 UI: test if image seems to exist when the user is filling up the “container image” in an external environment
• 👩‍💻 UI: update the admin panel to support editing resource pools with access to HPC sessions
• 🚫 UI: show a prominent warning when a data connector is created with insecure permissions
• ⏩ Sessions: skipping a data connector means “do not mount” now instead of trying to mount invalid configurations which would prevent sessions from starting
• 📊 Metrics: identify users when metrics collection is enabled

🐞 Bug Fixes

• UI: align footer bar when creating or editing a data connector
• UI: fix web socket connections recreated on every page
• UI: fix broken documentation links in the admin panel
• Sessions: sessions can be launched after a project copy without rebuilding
• UI: fix wrong pagination in the group search page
• UI: fix Renku legacy warning displayed on unrelated code repositories
• API: fix patching of resource pools where default or public would revert to false
• Sessions: fix issue where session secrets creation would conflict with existing secrets
• Backend: fix issue with Prometheus metrics when running in OpenShift

Internal Changes

Improvements

• Backend: run background tasks as a single process

Notes for Renku Administrators

⚠️ Upgrade for csi-rclone to v0.4.3: Deploying the Renku upgrade will also upgrade csi-rclone to v0.4.3 which means all sessions should be paused during the upgrade.

Individual components

• renku-data-services v0.60.0
• renku-ui v4.11.0
• csi-rclone v0.4.3

2.9.0

Renku 2.9.0 introduces support for running sessions on CSCS, accessing private Docker images and several other fixes and improvements.

User-Facing Changes

🌟 New Features

• 🐸 Sessions: Renku now supports remote sessions on CSCS! Contact us to get started.
• 🐸 Sessions: Add support for using private container images in sessions. Integrations are used to allow Renku to use private images from GitHub and GitLab on behalf of the user.

✨ Improvements

• API: Allow admins to setup platform redirects
• Projects: Show warnings on code repositories and session launchers in Renku projects that reference the RenkuLab GitLab

⏳ Next Phase of Decommissioning Renku Legacy (end of October 2025)

These features will be enabled on renkulab.io when Renku Legacy is shut down on October 2025

• Legacy Projects: Redirect Renku Legacy URLs to current Renku 2.0 project, if one is known
• Legacy Projects: Show a warning page in place of Renku Legacy project pages with migration instructions

🐞 Bug Fixes

• Sessions: fix an issue where node affinities set up by admins on resource classes would not result in correct pod scheduling
• Sessions: fix an issue where code-based builds would be incorrectly marked as failed

Internal Changes

Improvements

• Sessions: Amalthea support for service accounts in OpenShift
• API: Add a new type of integration oidc_generic to allow integrations implementing OpenID Connect as their authentication provider
• API: Explicitly specify the ingress class name for remote clusters.

Bug Fixes

• Sessions: Add custom CA certificates to the sidecar containers in sessions that were missing them.

Notes for Renku Administrators

Information about whether upgrading to this version requires or causes an outage, interrupts sessions or introduces significant changes to the Helm chart.

• This release contains an update to the Amalthea Session CRD, update it manually if you do not deploy Renku with amalthea.deployCrd=true .

Individual components

• amalthea 0.22.0
• renku-data-services v0.57.0
• renku-data-services v0.58.0
• renku-data-services v0.59.0
• renku-ui v4.9.0
• renku-ui v4.10.0

2.8.0

Renku 2.8.0 introduces some new features and bug fixes.

User-Facing Changes

🌟 New Features

• Data services: Preliminary support for external Kubernetes clusters.
• Data services: Add option to decouple the internal Gitlab.
• Data services: Handle private images from the internal Gitlab.

✨ Improvements

• UI: update the “Get Started” link in the footer bar
• Sessions: Improve handling for autoscale events for sessions in Kubernetes.

🐞 Bug Fixes

• Data services: Do not save invalid build from code environments.
• UI: fix text alignment for long keywords
• UI: do not show “copied from” when the source project is inaccessible
• UI: avoid environment description overflow
• UI: fix global environment update in the admin panel
• Sessions: Use a mirrored Bitnami image for authentication that will keep working even with the deprecation of the official Bitnami images.
• Sessions: Properly consider the last HTTP request time when determining idleness.

Internal Changes

Improvements

• Gateway: Make it possible to disable legacy (v1) services but keep the internal Gitlab still functioning the same as in legacy Renku.

Bug Fixes

• Data services: add missing entity slug constraints
• Data services: properly determine build run status

Notes for Renku Administrators

There is a new flag in the values file calledenableInternalGitlab, set to true by default. This flag indicates that the Gitlab that comes with legacy (V1) Renku should still be used. If the value is set to false then the gateway will not ask users to log into the Renku legacy Gitlab and will not inject credentials for it. Note also that the enableInternalGitlab flag cannot be set to false if the enableV1Services flag is set to true. If you are creating a brand new deployment of Renku, then both the enableInternalGitlab and the enableV1Services flags should be set to false.

Individual components

• renku-ui 4.8.0
• amalthea 0.21.0
• amalthea 0.21.1
• renku-data-services 0.56.0
• renku-gateway 1.7.0

2.7.1

Renku 2.7.1 introduces a fix to Amalthea that enables Renku user sessions to function even with the deprecation of Bitnami images.

User-Facing Changes

🐞 Bug Fixes

• Sessions: Use a mirrored Bitnami image for authentication that will keep working even with the deprecation of the official Bitnami images.

Notes for Renku Administrators

None.

Individual components

• amalthea 0.20.2

2.7.0

Renku 2.7.0 introduces some new features and bug fixes.

User-Facing Changes

🌟 New Features

• Sessions: add a new frontend for session environments built from code, ttyd , which is a minimalist web-terminal

✨ Improvements

• Integrations: add support for GitHub Enterprise Server
• UI: add the option to change a project’s slug in the settings page

🐞 Bug Fixes

• UI: fix the broken links from Renku Legacy search page
• Sessions: move the git proxy port into the reserved range for sessions, allowing users to pick port 8080
• Sessions: fix an issue where admins could not create or update global session environments

Notes for Renku Administrators

The git-proxy sidecar container in sessions has been updated to have ports configured inside the reserved range
for session services (range 65400-65535). Previously, the ports 8080 and 8081 were used which would break sessions
configured with either port (custom session environments). These ports can be configured via the helm chart with the 2 fields:

• notebooks.gitHttpsProxy.port to set the git-proxy port
• notebooks.gitHttpsProxy.healthPort to set the git-proxy health check port

However their defaults in the helm chart are correct and in the desired reserved range. So changing these default values is not necessary.

Individual components

• renku-data-services 0.55.0
• renku-notebooks 1.31.0
• renku-notebooks 1.31.1
• renku-ui 4.7.0

2.6.2

Renku 2.6.2 introduces a few fixes related to the sunsetting of Renku Legacy.

User-Facing Changes

✨ Improvements

• Data services: prevent users from starting new v1 sessions from the API when they are supposed to be disabled. Previously, users would still be able to start v1 sessions from the API even if the UI would tell them otherwise.

Internal Changes

Bug Fixes

• Data services: configure the K8s watcher to not attempt to watch v1 sessions when v1 services are not deployed.

Notes for Renku Administrators

None.

Individual components

• renku-data-services 0.54.0