Update testing node-manager charts #69
Merged
Conversation
This file contains 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
Signed-off-by: Cooper Tseng <[email protected]>
Vicente-Cheng
approved these changes
Jan 6, 2025
bk201
approved these changes
Jan 6, 2025
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 pr basically copy content in https://github.com/harvester/charts/tree/release/charts/harvester-node-manager to node-manager charts.
The chart in node-manager is intended for testing usage. Github actions will trigger the
deploy_nm.shto deploy the latest release of node-manager to the vagrant-rancher cluster 0 (now latest nm release chart is v0.3.3), then the node manager chart will be upgraded to the version in the node-manager repo 1.Please not that it is necessary to sync the node-manager charts between this repo and https://github.com/harvester/charts/tree/master/charts/harvester-node-manager (master branch) to ensure that the CI pipeline tests the upgrade path correctly, from the latest release to the development version.