fix: make the legacy services flag work#4067
Conversation
|
You can access the deployment of this PR at https://ci-renku-4067.dev.renku.ch |
1f59942 to
7951277
Compare
7951277 to
9622433
Compare
9d40f98 to
bb8c8ed
Compare
| port: | ||
| name: {{ $keycloakServicePort }} | ||
| {{- end }} | ||
| - path: /gitlab |
There was a problem hiding this comment.
Moved further down in the file in an if statement that templates this only when v1 services are enabled.
| name: {{ template "renku.fullname" $ }}-gateway | ||
| port: | ||
| number: 80 | ||
| - path: /repos |
There was a problem hiding this comment.
Moved further down in the file in an if statement that templates this only when v1 services are enabled.
| name: {{ template "renku.fullname" $ }}-gateway | ||
| port: | ||
| number: 80 | ||
| - path: /entities |
There was a problem hiding this comment.
Moved further down in the file in an if statement that templates this only when v1 services are enabled.
aledegano
left a comment
There was a problem hiding this comment.
What a day to be alive!!! 🥳
LGTM!!!
lorenzo-cavazzi
left a comment
There was a problem hiding this comment.
Looks good!
Should it be paired with this work that supports disabling the UI side?
SwissDataScienceCenter/renku-ui#3730
a701356 to
621c303
Compare
|
@lorenzo-cavazzi yes Sekhar will rebase and use this flag in the work he is doing when this is merged. |
|
Tearing down the temporary RenkuLab deployment for this PR. |
* chore: remove old search deployments and values (#4069) * fix: make the legacy services flag work (#4067) * feat: upgrade ui to 4.2.0 (#4075) * chore: simplify ui config for openshift (#4065) * feat: upgrade amalthea to 0.20.0 (#4076) * refactor: harmonize security context handling (#4077) securityContext content was defined in multiple different manifests. Their content being hard coded there made them unsuitable for modifications such as required for OpenShift deployment. This patch makes them all use the content coming from the values file since they were mostly all using the same values. * chore: reconcile the two security contexts PRs (#4074) --------- Co-authored-by: Tasko Olevski <tasko.olevski@sdsc.ethz.ch> * refactor: move service account creation to own template (#4080) * feat: upgrade ui to 4.2.1 (#4082) --------- Co-authored-by: Renku Bot <renku@datascience.ch> Co-authored-by: Samuel Gaist <samuel.gaist@idiap.ch> Co-authored-by: Chandrasekhar Ramakrishnan <ciyer@users.noreply.github.com>
* chore: remove old search deployments and values (#4069) * fix: make the legacy services flag work (#4067) * feat: upgrade ui to 4.2.0 (#4075) * chore: simplify ui config for openshift (#4065) * feat: upgrade amalthea to 0.20.0 (#4076) * refactor: harmonize security context handling (#4077) securityContext content was defined in multiple different manifests. Their content being hard coded there made them unsuitable for modifications such as required for OpenShift deployment. This patch makes them all use the content coming from the values file since they were mostly all using the same values. * chore: reconcile the two security contexts PRs (#4074) --------- Co-authored-by: Tasko Olevski <tasko.olevski@sdsc.ethz.ch> * refactor: move service account creation to own template (#4080) * feat: upgrade ui to 4.2.1 (#4082) --------- Co-authored-by: Renku Bot <renku@datascience.ch> Co-authored-by: Samuel Gaist <samuel.gaist@idiap.ch> Co-authored-by: Chandrasekhar Ramakrishnan <ciyer@users.noreply.github.com>
/deploy extra-values=enableV1Services=false