WIP: UI-specific configuration of legacy support (do not merge)

Author: ciyer

helm-chart/renku/templates/ui/ui-client-deployment-template.yaml

@@ -99,7 +99,7 @@ spec:
             - name: IMAGE_BUILDERS_ENABLED
               value: {{ .Values.dataService.imageBuilders.enabled | quote }}
             - name: LEGACY_SUPPORT
-              value: {{ printf "{\"enabled\": %t }" .Values.enableV1Services | quote }}
+              value: {{ toJson .Values.ui.client.legacySupport | quote }}
           livenessProbe:
             httpGet:
               path: /

helm-chart/renku/values.yaml

@@ -675,6 +675,10 @@ ui:
       # overrides:
       #   9: "/"
       #   10: "/"
+    # Configuration to enable/disable support for Renku legacy pages
+    legacySupport:
+      # Set this to "false" to disable support for Renku legacy
+      enabled: true
     # Configuration to display the "email us" message on the session class selector.
     sessionClassEmailUs:
       # Set this to "true" to enable the "Need more compute resources? Email us!" message

helm-chart/values.yaml.changelog.md

@@ -11,6 +11,7 @@ Please follow this convention when adding a new row
 
 This will result in 2 fewer deployments in your cluster. If the values are left in the values file they will be ignored. Therefore this does not require immediate action by administrators, it is just good practice to remove deprecated sections that you may have in your values file.
 
+* NEW ``ui.client.legacySupport`` to control whether Renku Legacy is supported in the UI.
 * DELETE `ui.client.podSecurityContext`, replaced by `podSecurityContext`
 * DELETE `ui.client.securityContext`, replaced by `securityContext`
 * DELETE `ui.server.podSecurityContext`, replaced by `podSecurityContext`