Releases: SwissDataScienceCenter/renku
Version 0.11.2
Minor release fixing a bug in the Renku template for Keycloak.
Version 0.11.1
This is a minor release featuring improvements to the Renku UI.
New Feature highlights:
- UI: updates to style of alerts, menus, and tables
- User sessions: allow stopping a session that is not fully started
- User sessions: support links for sharing sessions with additional options
Note: this release also updates the version of the keycloak chart to 16.0.4
, but no manual admin action should be needed.
For full release notes see:
Version 0.11.0
This is a major release that includes an important upgrade to GitLab and PostgreSQL components: 14
and 12
major versions respectively.
Upgrading from 0.10.3
BREAKING CHANGES
Please follow these instructions and read the GitLab update documentation carefully before applying the upgrades.
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.10.3
This is a bugfix release that includes various fixes to user sessions and some improvements to the UI.
Improvements
- Datasets: allow canceling a search before it completes.
- User sessions: rearrange session menu options.
- User sessions: update Renku commands cheat sheet.
- UI: notify user when a new renkulab version is available.
- File display: highlight code syntax in markdown files.
- File display: support preview of Matlab files.
- File display: add PDF file viewer.
- File display: render LaTeX math.
Bug fixes
- User sessions: CPU limit enforcement is now configurable. Admins should refer to the values documentation to configure this in a Renku deployment.
- User sessions: keep auto-saved branches after restoring a session with a newer commit.
- User sessions: a different package is used to decode sessions authorization token.
- Anonymous sessions: not crash anonymous sessions if these are disabled in a deployment.
Individual components
For a full list of improvements and bug fixes in individual components, please check:
Upgrading from 0.10.2
- A new secret is needed in
redis.password
, this can be generated randomly withopenssl rand -hex 32
or similar.
Version 0.10.2
This is a bugfix release that includes various fixes and improvements to user sessions.
See renku-notebooks 1.2.0 and amalthea 0.2.1 for more details.
Improvements
- Chart: Add
tolerations
,affinity
andnodeSelector
for user sessions.
Bug fixes
- User sessions: checkout the correct alternative branch.
- User sessions: use correct fallback renku image.
- Anonymous sessions: fix failing probes.
Upgrading from 0.10.1
A couple of value updates are needed for upgrading to 0.10.2
- A new secret is needed in
global.uiserver.clientSecret
, it can be randomly generated usingopenssl rand -hex 32
. - For the time being, Amalthea's resource usage check needs to be disabled. Please set
notebooks.amalthea.resourceUsageCheck.enabled
tofalse
. - If your deployment has user session dedicated nodes, please add the corresponding label
renku.io/node-purpose=user
and taintrenku.io/dedicated=user
withNoSchedule
effect. Also, configure the sessions to add the corresponding toleration and affinity inside thenotebooks
section of the values file:
sessionTolerations:
- key: renku.io/dedicated
operator: Equal
value: user
effect: NoSchedule
sessionAffinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: renku.io/node-purpose
operator: In
values:
- user
Version 0.10.1
This is a bugfix release that contains a fix for launching R sessions with our newest component that manages user sessions (Amalthea).
See renku-notebooks 1.1.1 and amalthea 0.1.3 for more details.
Improvements
Our documentation has been restructured, now articles are reorganized into Tutorials
, How-to guides
, Topic Guides
and Reference
(see #2191).
Version 0.10.0
This release includes a new user session controller replacing Jupyterhub. The new controller is not compatible with user sessions created by Jupyterhub, therefore all user sessions need to be terminated prior to upgrading to 0.10.0
.
Improvements
- Documentation: updated documentation on proper teaching etiquette and steps to use renkulab for teaching.
- User sessions: use Amalthea to control sessions through a k8s operator.
Bug fixes
- Authentication: log out from GitLab when logging out from Renku.
- Authentication: fix Keycloak token authentication.
Individual components
For a full list of improvements and bug fixes in individual components, please check:
Upgrading from 0.9.3
BREAKING CHANGES!! The admin should plan and warn users ahead of time that their sessions will be terminated when doing the upgrade. The new Loud
statuspage component introduced in 0.9.3
can help get the message across.
- The use of Amalthea and removal of Jupyterhub will require some changes. Namely:
- All references to Jupyterhub in the
values.yaml
have been removed and are not required anymore. - Amalthea is installed from a separate helm chart which is now a dependency of the
renku-notebooks
helm chart. - Several new sections have been added to the
values.yaml
file which are required by Amalthea. Please refer to the renku values file for more details.
- All references to Jupyterhub in the
- Some older images with Rstudio will open Rstudio in a directory one level above the repository. This can be fixed by upgrading to a newer version of the base image in the Dockerfile in the relevant renku project.
- This version is not backward compatible with the user sessions from older versions. During the deployment the admin should clean up all remaining user sessions and then deploy this version.
- Anonymous sessions do not require a separate namespace and renku-notebooks deployment, if enabled in the values file they now run in the same namespace as regular user sessions.
Version 0.9.3
Improvements
This is a very minor release that allows messages about maintenance and downtime to be displayed more prominently in the UI. It is necessary because the interruptions from upcoming releases can be more effectively communicated to users.
- UI: more persistent notifications for maintenance or downtime
Version 0.9.2
This is a bugfix release that includes various minor fixes: templates and core use a new bugfix CLI version, as well as other fixes for external to SDSC deployments and improved login style.
Improvements
- Sessions: make enforced limits configurable when using
emptyDir
disk space.
Bug Fixes
- Templates: Renku and custom templates updated to use Renku
0.16.2
(should fix pyshacl and renku conflicting dependencies). - Renku core / CLI: pin pyshacl to version
0.17.0.post1
. - Login: make social identity providers style match internal ones.
- UI: configurable welcome page for external deployments.
Individual components
For a full list of improvements and bug fixes in individual components, please check: