Skip to content

2.11.0

Latest
Latest

Choose a tag to compare

View all tags
@olevski olevski released this 12 Dec 12:54
2.11.0
bcf8278
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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

Assets 2
Loading