Use Longhorn for storage #13
Merged
Conversation
This file contains hidden or 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
Contributor
Author
|
@Gertmeister or @sofusalbertsen would one of you maybe like to take this and fill in the lots and lots of info that's missing? <3 |
Collaborator
|
I haven't worked with Longhorn so I'm afraid I have nothing to add here 😞 |
housa
force-pushed
the
longhorn_as_storage_solution
branch
from
874c518 to
fcad517
Compare
…, and decision outcome
sofusalbertsen
requested review from
Gertmeister,
moller2866 and
sofusalbertsen
as code owners
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 is a suggestion to use Longhorn as the storage solution, justification is placed in the ADR, which is linked from the decision matrix.
currently a work in progress, justification basically not added yet. Feel free to fill in your opinions. 😁