Releases: SwissDataScienceCenter/renku-notebooks
Version 1.7.0
1.7.0 (2022-05-16)
Bug Fixes
- app: eliminate unnecessary gitlab calls (#1035) (3ff58d5)
- app: keep git-proxy alive on session shutdown (#951) (7589230)
Features
Breaking changes
The value securityContext.enabled
in the notebook service values.yaml
used to be used in much older versions and has since been deprecated. However, it may still be used in your values.yaml
file. If this is the case it will cause problems when deploying because with this release the securityContext
field is directly added as the security context for every container in the notebook service. You can correct this by simply removing this field from your values file along with its parent securityContext
field, this will make the notebook service use the default security context which functions properly.
Version 1.6.2
Version 1.6.1
Version 1.6.0
Version 1.5.1
Version 1.5.0
1.5.0 (2022-03-15)
Features
- app: better messages on session launch fail (#923) (a8636e3)
- app: return logs from all containers (#887) (3defae5)
- app: version endpoint (#938) (4c2b26d)
BREAKING CHANGES
- The status of the session is reported in a different more compact form in the API. This affects the
/servers
or/servers/<server_name>
endpoints. - The logs from all containers in the session (including init containers) are returned, not just the logs from the
jupyter-server
container. This affects the/notebooks/logs/<server_name>
endpoint. - The logs from
/notebooks/logs/<server_name>
are returned as a dictionary of strings where the key is the container name and the string is the log.
Version 1.4.1
Version 1.4.0
1.4.0 (2022-02-15)
Features
Bug Fixes
- app: modify terminology for mounting S3 buckets (#922) (9f93dcf)
- chart: allow mounting of S3 buckets to be enabled without installing Datashim (#922) (9f93dcf)
Breaking changes
The impact of the following breaking changes is minor because they only affect deployments that mount S3 buckets in user sessions. However as this is an experimental feature that was released very recently (and is turned off by default) it is very unlikely that any users are affected by this. Only users who have enabled S3 bucket mounting in sessions in 1.3.0
and are using this will be affected by this change.
- the API endpoints that start user sessions or list them use
cloudstorage
in their request/response schemas rather thans3mounts
- the values for the Helm chart related to mounting S3 buckets have also changed to use
cloudstorage
instead ofs3mounts
, and the setupt for mounting S3 buckets can be found undercloudstorage.s3
Version 1.3.0
Version 1.2.1
1.2.1 (2021-12-01)
Bug Fixes
- app: apply CPU limits to user sessions (#826) (29d44a2)
- app: do not delete autosaves before restoring (#814) (32f6c5e)
- app: use 3 scenarios for session cpu limits (#828) (ff7899d)
- app: use pyjwt to decode token (#818) (4987db1)
- app: user not authenticated and anonymous sessions not allowed (#829) (edb9c03)