Releases: SwissDataScienceCenter/renku
2.17.2
2.17.1
Renku 2.17.1 updates Amalthea to increase restrictions in the security context for sessions.
User-Facing Changes
🐞 Bug Fixes
- Amalthea: Add capabilities.drop=ALL to all container security contexts.
Individual Components
2.16.4
Renku 2.16.4 updates Amalthea to increase restrictions in the security context for sessions.
User-Facing Changes
🐞 Bug Fixes
- Amalthea: Add capabilities.drop=ALL to all container security contexts.
Individual Components
2.17.0
Renku 2.17.0 introduces changes to the integrations page and user flows, as well as several internal improvements.
User-Facing Changes
✨ Improvements
- UI: improve the UX of using RenkuLab integrations
- UI: improve selecting existing data connectors when adding them to a project
- UI: add meta tags to group and user pages
- UI: render markdown tables in project documentation, privacy policy and terms of service
🐞 Bug Fixes
- UI: fix the resource class selection when creating a new session launcher
- Build from code: set session launcher parameters correctly when the build finishes
- Team: changelog item, alphabetized by team name
Internal Changes
Improvements
- Sessions: use internal tokens for session sidecar services
- Amalthea: setup Sentry traces
- Amalthea: add configuration to rewrite session images to use a proxy-cache
- UI Server: remove dependency on Redis
Notes for Renku Administrators
- Sessions need to be paused during the upgrade.
- A newer version of the build strategy
renku-buildpacks-v3needs to be installed for Shipwright builds.
Individual components
2.16.3
Renku 2.16.3 fixes a bug in the data service related to building images from code.
User-Facing Changes
🐞 Bug Fixes
- Data service: Determine the status of the build runs for images built from code.
Individual Components
2.16.2
Renku 2.16.2 fixes a bug in the data service related to the new R buildpacks.
User-Facing Changes
🐞 Bug Fixes
- Data service: Proprely set the option to strip the URL prefix for R environments built from code.
Individual Components
2.16.1
Renku 2.16.1 fixes a bug in the new buildpacks for R.
User-Facing Changes
🐞 Bug Fixes
- Buildpacks: Fixed an issue that prevented R environments building in the R buildpacks.
Individual Components
2.16.0
Renku 2.16.0 introduces support for publishing datasets to Zenodo directly from RenkuLab, experimental support for RunAI as a session backend, and a number of bug fixes and internal improvements. Please read on for more details.
User-Facing Changes
🌟 New Features
- Dataset deposits to Zenodo: Users can now publish datasets directly to Zenodo from within RenkuLab, making it easier to share and cite research data with a permanent DOI.
- R and RStudio environment variants: The buildpacks have been updated to
0.4.0with support for R and RStudio session variants.
🐞 Bug Fixes
- Sessions: Fixed an issue where sessions would not correctly return a 404 response when a session could not be found.
- Sessions: Fixed incorrect CPU quantity being reported or applied for session resource requests.
- Sessions: Fixed an error with cloning repository token URLs that could prevent sessions from starting.
- Sessions: Improved error messages shown when an invalid builder/frontend variant combination is specified.
- Authentication: Fixed handling of missing JWK (JSON Web Keys) during authentication flows.
- Helm chart / Keycloak: Fixed an issue where the service account user fetch was called unconditionally for all OAuth clients, causing failures for clients that do not use the
client_credentialsflow (fixes #4373).
Internal Changes
Improvements
- Sessions: Added support for RunAI as a remote backend for Amalthea sessions. This is an experimental feature for deployments that use RunAI for GPU scheduling.
- Sessions: Anonymous sessions now receive an appropriate Kubernetes label, improving observability and management of anonymous workloads.
- Buildpacks: Updated buildpacks to
0.4.0, which adds R and RStudio support and general dependency updates. - Amalthea: Upgraded Amalthea to
0.27.2.
Bug Fixes
- Backend: Guarded the service account user fetch behind an
oauth_flowcheck so that clients not usingclient_credentialsno longer cause errors on startup or modification. - Backend: Fixed token URL construction when cloning repositories in sessions.
- Amalthea: Fixed a bug where the reconciling of paused sessions caused a lot of reconcile loop invocations and generated a lot of logs.
Notes for Renku Administrators
- The preliminary RunAI backend support introduced in this release is opt-in and requires additional configuration. No action is needed if you are not using RunAI. This is still not usable from the UI for general consumption. Stand by for more news on this in subsequent releases.
- If you have enabled resource request tracking (
dataService.dataTasks.enableResourceRequestTrackingin the values file) introduced in2.15.0, be aware that this feature continues to add database load — monitor disk space and query performance accordingly.
Individual Components
2.15.3
Renku 2.15.3 introduces a bug fix to handle the FirecREST API upgrade to 2.5.0 which prevented remote HPC sessions from starting.
User-Facing Changes
🐞 Bug Fixes
- Sessions: Fix handling of remote HPC sessions using the FirecREST API 2.5.0.
Individual components
2.15.2
Renku 2.15.2 introduces a bug fix to gracefully handling missing or invalid JWT signing keys. When the keys cannot be found the JWT is considered invalid a 401 status is returned, rather than a 500 code. The 401 code is then properly handled by the UI which asks the user to log in again.
User-Facing Changes
🐞 Bug Fixes
- Backend: Fix handling of missing JWT signing keys when validating tokens.