[Kubernetes] Introduce on-prem persistent Storage (Longhorn) 🎉 #979
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
YuryHrytsuk
changed the title
Extra: introduce longhorn pv vales for portainer
Since we use a dedicated disk for LH, we can go ahead with 5%
YuryHrytsuk
force-pushed
the
kubernetes-introduce-longhorn
branch
from
47dc79c to
a726c66
Compare
YuryHrytsuk
changed the title
YuryHrytsuk
changed the title
YuryHrytsuk
changed the title
mrnicegyu11
reviewed
May 6, 2025
mrnicegyu11
reviewed
May 6, 2025
mrnicegyu11
reviewed
May 6, 2025
mrnicegyu11
reviewed
May 6, 2025
mrnicegyu11
reviewed
May 6, 2025
mrnicegyu11
approved these changes
May 6, 2025
mrnicegyu11
pushed a commit
to mrnicegyu11/osparc-ops-environments
that referenced
this pull request
May 9, 2025
…oundation#979) * Introduce longhorn chart * Further longhorn configuration * Longhorn: further settings configuration * Fix longhorn configuration bugs Extra: introduce longhorn pv vales for portainer * Add comment for deletion longhorn * Further longhorn configuration * Add README.md for Longhorn wit FAQ * Update Longhorn readme * Update readme * Futher LH configuration * Update LH's Readme * Update Longhorn Readme * Improve LH's Readme * LH: Reduce reserved default disk space to 5% Since we use a dedicated disk for LH, we can go ahead with 5% * Use values to set Longhorn storage class * Update LH's Readme * LH Readme: add requirements reference * PR Review: bring back portainer s3 pv * LH: decrease portinaer volume size
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.
What do these changes do?
Introduce storage for on premise deployment: Longhorn.io. This lets us running (as-of-now) non-critical services with data volumes without binding these services to any particular node (Longhorn will replicate data volumes across multiple nodes)
Extra features
Documentation
README.mdand comments invalues.yaml.gotmplto get additional insights into configuration and gotchas.Warnings⚠️
README.mdfor more information.FYI: @matusdrobuliak66 @sanderegg
ToDo
Related issue/s
Related PR/s
Relevant [info] resources
Checklist
General:
New Stack:
New Service:
Service's Public URL is included in maintenance mode--> no maintenance mode for Kubernetes as of now