fix(helm): rewrite chart with Kubernetes deployment fixes #313
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.
Summary
Rewrites the
.helm/chart to fix all known Kubernetes deployment issues from #119. Tested and verified on a production cluster.Fixes
_helpers.tplhostwas a list instead of a scalarencryptAESwithrandAlphaNum+b64enc--log-bin-trust-function-creators=1/var/run,/tmp,framework/cache,framework/sessionsas emptyDirS6_CMD_WAIT_FOR_SERVICES_MAXTIME=300000@paramannotations,global.storageClass,existingClaimsupportTested on
Migration notes
Two Cattr migrations have duplicate table/column creation that fail on fresh installs:
2020_07_21_095849_create_redmine_instances_table— table already created by2020_06_01migration2023_03_09_224051_upgrade_laravel_sanctum_to_3_0—expires_atcolumn already existsWorkaround documented in the related issue #312.
Test plan
helm lint .helm/passeshelm template .helm/renders valid YAMLhelm installon a fresh cluster deploys MySQL + CattrResolves #119
Related: #312