Skip to content

Conversation

@sgaist
Copy link
Collaborator

@sgaist sgaist commented Dec 11, 2025

Describe your changes

This PR removes the enableV1Services flag as well as all the resources behind it from the helm chart.

Issue(s) ticket number(s) and link(s)

Fixes #4280

/deploy #slow

@sgaist sgaist requested review from a team as code owners December 11, 2025 15:08
@rokroskar
Copy link
Member

I guess this replaces #4279 ?

@sgaist
Copy link
Collaborator Author

sgaist commented Dec 12, 2025

Replaces or complements
I discussed with @leafty and she told me I should move forward with my PR.

@leafty
Copy link
Member

leafty commented Dec 12, 2025

yes, no problem, close #4279 if we already have a superset of the changes here.

Copy link
Member

@olevski olevski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mentioned a few extra things that can be removed. If you want you can also do them in a followup PR.

test:
enabled: false
## Configuration for renku-graph services
graph:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few more things can be removed:

  • .global.core
  • .global.graph
  • .dlf-chart
  • .jena

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are even a few more sections that can be removed. But these "other sections" I did not mention above, because they all need code changes in the data service before we can remove them from here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seeing the conflict in values.yaml, is the dlf-chart still to be removed ?

@olevski
Copy link
Member

olevski commented Dec 15, 2025

Oh and please add /deploy to this. To make sure we get a ci deployment and the helm chart works.

@sgaist sgaist force-pushed the refactor/remove-obsolete-items branch from c1f59bd to 479fadd Compare December 16, 2025 09:30
@RenkuBot
Copy link
Collaborator

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

@olevski olevski changed the base branch from release-2.12.0 to release-2.13.0 December 22, 2025 09:57
Explicitly hard code it and webhooks as
to-be-removed as they are v1 only features
@sgaist sgaist force-pushed the refactor/remove-obsolete-items branch from af18a1f to b4b5906 Compare January 7, 2026 08:36
Copy link
Member

@leafty leafty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UI is broken by this change. Will push fix to the PR.

Comment on lines -106 to -107
- name: LEGACY_SUPPORT
value: {{ dict "enabled" .Values.enableV1Services "supportLegacySessions" .Values.ui.client.supportLegacySessions | toJson | quote }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to keep this configuration around for now.

@leafty leafty self-requested a review January 7, 2026 12:28
Copy link
Member

@leafty leafty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Look good, we need to test with gitlab.

Copy link
Member

@leafty leafty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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.

6 participants