refactor(storage): storage should be created outside of helm releases #62
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
storage resources created inside helm releases cause issues when upgrading said helm releases. creating these PVCs outside of the helm release cycle will allow charts to upgrade without the need for creating the storage itself, thereby avoiding inevitable helm release failures upon running an upgrade. BREAKING CHANGE: backing storage mechanism reworked; should likely only be merged after hardware cutover in #61 #61
k0s proved to be more difficult in the long run when working with raspberry pis. moving to the standard k3s deployment using ansible seemed like the right move to make considering that k3s is tested and proven on raspberry pi and the setup is just as easy. `gilt` is being used to pull in a playbook so that i dont have to clutter this repo any more than it already is. i've also added more directions on how to set the cluster up on the initial go. good luck and dog bless. BREAKING CHANGE: k0s no longer works, long live k3s #61
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.
storage resources created inside helm releases cause issues when upgrading said helm releases.
creating these PVCs outside of the helm release cycle will allow charts to upgrade without the need
for creating the storage itself, thereby avoiding inevitable helm release failures upon running an
upgrade.
BREAKING CHANGE: backing storage mechanism reworked; should likely only be merged after hardware
cutover in #61
#61