Skip to content

feat: Upgrade Keycloak to v26.4.0#4402

Merged
olevski merged 14 commits into
release-2.18.0from
upgrade_keycloak_26
Jun 24, 2026
Merged

feat: Upgrade Keycloak to v26.4.0#4402
olevski merged 14 commits into
release-2.18.0from
upgrade_keycloak_26

Conversation

@aledegano

Copy link
Copy Markdown
Contributor

/deploy

@aledegano aledegano requested a review from a team as a code owner March 16, 2026 11:34
@RenkuBot

Copy link
Copy Markdown
Collaborator

You can access the deployment of this PR at https://ci-renku-4402.dev.renku.ch

Base automatically changed from release-2.16.0 to master April 15, 2026 14:17
@olevski

olevski commented Apr 15, 2026

Copy link
Copy Markdown
Member

This was originally targeting release 2.16.0. But that was merged. So I moved it over to 2.17.0

@olevski olevski changed the base branch from master to release-2.17.0 April 15, 2026 14:27
@leafty leafty changed the base branch from release-2.17.0 to release-2.18.0 May 7, 2026 09:51
lorenzo-cavazzi and others added 10 commits June 2, 2026 10:27
* chore: bump ui to 4.14.0 and data-services to 0.75.0
* chore: update rbac for auto pausing sessions

---------

Co-authored-by: Tasko Olevski <16360283+olevski@users.noreply.github.com>
* chore: bump UI to 4.25.0
* tests: update matching session launcher title (#4467)
Currently we only support secrets. But in a lot of cases you can create
a configmap, annotate it and then k8s will populate it with
cluster-specific CA certs. This is an option for the internal image
registry that comes with openshift. And the auto-population with the
cert works only on configmaps, not on secrets.
Since we are using a full stack framework now the UI deployment is
making API calls for the UI. So it needs any self-signed certs just like
the ui server.
…#4428)

* feat: add configuration options for building image from private repositories

* feat: add configuration for session private image pull secret

This supplements the building part allowing to use independent
secrets for pushing during build and pulling for session
creation.

This secret is not accessible by the user.

* refactor: move private repo build support under a feature flag

Renku admins thus have the choice to provide builds only for
public repositories or for both.

* chore: add documentation for admins

* chore: add changelog entries for values file

---------

Co-authored-by: Flora Thiebaut <flora.thiebaut@sdsc.ethz.ch>
Use the new git-clone image from the amalthea repository (`renku/cloner`).

See: SwissDataScienceCenter/amalthea#1083
@olevski olevski requested review from a team as code owners June 24, 2026 12:00
@olevski olevski enabled auto-merge (squash) June 24, 2026 12:01
@olevski olevski merged commit de59da6 into release-2.18.0 Jun 24, 2026
42 of 43 checks passed
@olevski olevski deleted the upgrade_keycloak_26 branch June 24, 2026 12:38
@RenkuBot

Copy link
Copy Markdown
Collaborator

Tearing down the temporary RenkuLab deployment for this PR.

olevski pushed a commit that referenced this pull request Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants