This repository has been archived by the owner on Mar 11, 2021. It is now read-only.
Increasing size of the 'claim-che-workspace' PVC to 2GB #784
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
|
This PR changes one or more of the template files. These changes are now available for testing: Launch in OpenShift.io and click the update tenant button |
Codecov Report
@@ Coverage Diff @@
## master #784 +/- ##
=======================================
Coverage 74.82% 74.82%
=======================================
Files 38 38
Lines 3202 3202
=======================================
Hits 2396 2396
Misses 602 602
Partials 204 204Continue to review full report at Codecov.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation
After increasing RAM to 7GB Hosted Che user is able to start an advanced workspace with multiple plugins / extensions enabled, but it is still not be possible to simply build a relatively small project in this workspace due to the PVC size that should be also increased.
Reasoning
Since Jenkins / build namespace was removed some time ago which included 1GB PVC we can consider adding this storage to the *-che namespace. Resource wise this should be safe since we do not increase the number of PVC and just relocating the storage that was available initially on openshift.io.
Process
Our current assumption is that after the cluster-wide tenant update during existing PVCs would be automatically resized but we need to verify it against prod-preview: