-
Notifications
You must be signed in to change notification settings - Fork 36
feat: deprecate running legacy services #4236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6701146 to
a0b752e
Compare
564167d to
8e62069
Compare
olevski
approved these changes
Nov 6, 2025
leafty
commented
Nov 6, 2025
olevski
pushed a commit
that referenced
this pull request
Nov 25, 2025
This update updates the default helm chart values to not deploy Renku legacy (v1) services. Deprecation notices are also documented; the enableV1Services key will be removed in the next Renku release.
olevski
pushed a commit
that referenced
this pull request
Dec 12, 2025
This update updates the default helm chart values to not deploy Renku legacy (v1) services. Deprecation notices are also documented; the enableV1Services key will be removed in the next Renku release.
olevski
added a commit
that referenced
this pull request
Dec 12, 2025
* feat: deprecate running legacy services (#4236) This updates the default helm chart values to not deploy Renku legacy (v1) services. Deprecation notices are also documented; the enableV1Services key will be removed in the next Renku release. If you wish to keep running V1 services then you should explicitly set this value to `true`. Note that the flag and all V1 services will be fully removed in the next release. * build: chart changes to support gitlab redirects (#4246) * chore: use retries for requests in Keycloak init (#4268) Without retries the job immediately restarts and it takes a long time to get a deployment up and running when the ingress TLS and domain name is slowly getting propagated. * feat: improve integrations, code repositories, forms (#4257) * fix integrations and show better feedback for code repositories * streamline form appearance * update Cypress tests to match the latest UI changes * bump renku-ui to 4.12.0 and renku-data-services to 0.61.0 * feat: build base images for linux/arm64 (#4249) Update the "Build global base images" workflow to build multi-platform images. * The `linux/amd64` image is build the same way as before * The `linux/arm64` image uses the CUDA variants of the renku buildpacks * feat: support image building for arm64 (#4228) Add support for building images for `linux/arm64` to be used when running sessions at CSCS. Other changes include support for storing the `platform` of resource pools and for getting `platform` information about container images. These changes help support users who want to run sessions on `linux/arm64`. * feat: add sentry to k8s watcher (#4225) * fix: add helm values change for platformOverrides (#4278) * feat: add prometheus metrics to UI (#4220) See: SwissDataScienceCenter/renku-ui#3889 * fix: add env variable for nodejs to use CA certs (#4282) * feat: Upgrade 1 major version of Keycloak (#4241) This upgrades the Helm chart for Keycloak from 2.1.0 to 2.2.2. Which results also in an upgrade of Keycloak from 20.0.1 to 21.1.1. --------- Co-authored-by: Flora Thiebaut <flora.thiebaut@sdsc.ethz.ch> Co-authored-by: Chandrasekhar Ramakrishnan <ciyer@users.noreply.github.com> Co-authored-by: Tasko Olevski <tasko.olevski@sdsc.ethz.ch> Co-authored-by: Lorenzo Cavazzi <43481553+lorenzo-cavazzi@users.noreply.github.com> Co-authored-by: Alessandro Degano <40891147+aledegano@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update updates the default helm chart values to not deploy Renku legacy (v1) services. Deprecation notices are also documented; the
enableV1Serviceskey will be removed in the next Renku release.