feat: remove internal gitlab #3297
Merged
Conversation
This file contains 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
|
@olevski can we refresh this and get it merged? |
3 tasks
Panaetius
force-pushed
the
release-0.60.0
branch
from
01b058f to
5aa1251
Compare
rokroskar
force-pushed
the
remove-internal-gitlab
branch
from
011f2ab to
63adb08
Compare
rokroskar
temporarily deployed
to
ci-renku-3297
GitHub Actions
Inactive
olevski
commented
Oct 21, 2024
rokroskar
temporarily deployed
to
ci-renku-3297
GitHub Actions
Inactive
rokroskar
dismissed
their stale review
based on the old old version of things
|
You can access the deployment of this PR at https://ci-renku-3297.dev.renku.ch |
aledegano
reviewed
Oct 21, 2024
Panaetius
force-pushed
the
release-0.60.0
branch
3 times, most recently
from
7502cda to
ee8bbeb
Compare
rokroskar
force-pushed
the
remove-internal-gitlab
branch
from
63adb08 to
8b8d779
Compare
|
@aledegano I added the blurb |
rokroskar
temporarily deployed
to
ci-renku-3297
GitHub Actions
Inactive
aledegano
approved these changes
Dec 3, 2024
rokroskar
temporarily deployed
to
ci-renku-3297
GitHub Actions
Inactive
rokroskar
temporarily deployed
to
ci-renku-3297
GitHub Actions
Inactive
rokroskar
force-pushed
the
remove-internal-gitlab
branch
from
84de292 to
43ca1f5
Compare
Panaetius
approved these changes
Dec 4, 2024
Merged
Panaetius
pushed a commit
that referenced
this pull request
Dec 18, 2024
Co-authored-by: Rok Roškar <[email protected]>
Panaetius
added a commit
that referenced
this pull request
Dec 19, 2024
* chore: create release 0.62.0 * chore: update redis helm chart to latest revision (#3843) * feat: remove internal gitlab (#3297) Co-authored-by: Rok Roškar <[email protected]> * Update search to release 0.7.0 (#3852) * fix: point redis helm chart to the oci URI (#3855) * tests: remove check of project container for anonymous users (#3853) * feat: add support for session secrets in Renku 2.0 (#3837) Closes #3832. Add support for session secret slots and session secrets in Renku 2.0. --------- Co-authored-by: Tasko Olevski <[email protected]> * chore: add note about polybox/switchdrive to the top changelog (#3856) * feat: update user and group pages design (#3857) Co-authored-by: Flora Thiebaut <[email protected]> * Update CHANGELOG.rst * Update CHANGELOG.rst --------- Co-authored-by: Lionel Sambuc <[email protected]> Co-authored-by: Tasko Olevski <[email protected]> Co-authored-by: Rok Roškar <[email protected]> Co-authored-by: eikek <[email protected]> Co-authored-by: Andrea Cordoba <[email protected]> Co-authored-by: Flora Thiebaut <[email protected]> Co-authored-by: Tasko Olevski <[email protected]> Co-authored-by: Rok Roškar <[email protected]> Co-authored-by: Ralf Grubenmann <[email protected]>
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 removes the omnibus gitlab helm deployment that is part of Renku.
We mentioned in our docs that we would deprecate this in the future. I think we should really get rid of it because the more we keep it around the more likely it is that someone will start running with it and then be stuck with the same migration problems that we had to go through.
The easiest/most simple demo of Renku should be done against gitlab.com or any other existing gitlab deployment. Deploying gitlab is NOT a simple thing. And combining that with rolling out Renku in one step is just too daunting.
We also really do not update/maintain/test the Gitlab helm chart. So we run the risk of someone deploying it and having problems or security issues because the helm chart is not up to date.
/deploy