-
Notifications
You must be signed in to change notification settings - Fork 31
Add Helm values.yaml migration process and docs: #260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #260 +/- ##
=======================================
Coverage 48.38% 48.38%
=======================================
Files 102 102
Lines 8649 8649
=======================================
Hits 4185 4185
Misses 4209 4209
Partials 255 255 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This automates tbe migration from the Helm chart version 0.6.2 to v0.19.1. Signed-off-by: Jacob Weinstock <[email protected]>
Signed-off-by: Jacob Weinstock <[email protected]>
Also, rename the migration file to be named to reference all v0.19 versions. Signed-off-by: Jacob Weinstock <[email protected]>
29077f3 to
2acfcb4
Compare
This means that no Go code is needed to be written and maintained. Signed-off-by: Jacob Weinstock <[email protected]>
The previous chart would install CRDs using the Helm install's kubeconfig permissions not the permissions of the tink-stack. This means that the rbac from v0.6.2 could be "role". This causes the v0.19.x Tinkerbell to fail to install CRDs because of insufficient permissions. Users can override this by modifying the v0.19.x values. Signed-off-by: Jacob Weinstock <[email protected]>
These are the updated instructions using the helm only migration process. Signed-off-by: Jacob Weinstock <[email protected]>
We can do the same thing with Helm. This means less new code to maintain. Signed-off-by: Jacob Weinstock <[email protected]>
Signed-off-by: Jacob Weinstock <[email protected]>
Signed-off-by: Jacob Weinstock <[email protected]>
Signed-off-by: Jacob Weinstock <[email protected]>
Signed-off-by: Jacob Weinstock <[email protected]>
Signed-off-by: Jacob Weinstock <[email protected]>
Docs and missed templated value. Signed-off-by: Jacob Weinstock <[email protected]>
Signed-off-by: Jacob Weinstock <[email protected]>
Signed-off-by: Jacob Weinstock <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds migration functionality to help users upgrade from the deprecated Tinkerbell Helm chart version 0.6.2 to the newer v0.19.x format. The migration automates the conversion of values.yaml configuration between the two chart versions.
- Introduces a migration template that converts 0.6.2 values to v0.19.x format
- Adds configuration option to enable migration functionality
- Provides comprehensive documentation with step-by-step migration instructions
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| helm/tinkerbell/values.yaml | Adds migration configuration option with documentation reference |
| helm/tinkerbell/templates/migration/from-0.6.2.yaml | Template that maps old chart values to new format for automated migration |
| docs/technical/HELM_VALUES_MIGRATION.md | Complete migration guide with prerequisites, steps, and examples |
Description
This automates the migration from the Helm chart version 0.6.2 to >= v0.19.1.
Why is this needed
Fixes: #124
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: