Fix image overrides for scale services#41
Merged
Conversation
👋 Thanks, @galt-tr!This pull request comes from a fork. For security, our CI runs in a restricted mode.
Thanks for contributing to bsv-blockchain/teranode-operator! 🚀 |
|
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
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 pull request updates the image override logic for several cluster components to ensure that the cluster-level image always takes precedence, regardless of any existing deployment overrides. It also improves the test coverage and reliability for cluster reconciliation, including more thorough validation of image propagation and resource cleanup. Additionally, it enhances the test setup for custom volumes and adds brief delays to allow for resource cleanup and deployment creation.
Image override logic updates:
cluster_asset.go,cluster_blockassembly.go,cluster_propagation.go, andcluster_subtreevalidator.gowas changed so that the cluster's image always overrides the component's deployment override image, ensuring consistency across all components. [1] [2] [3] [4]Test improvements for cluster reconciliation:
cluster_controller_test.gonow verify that enabling additional components (Propagation,SubtreeValidator,Pruner) correctly propagates the cluster image to those components, and that updating the cluster image triggers reconciliation and updates all relevant components. [1] [2]Custom volume setup in tests:
EmptyDirsources, improving the accuracy and reliability of volume-related test scenarios.Minor test and naming updates:
blockvalidator_controller_test.gofor clarity, and commented out unused reconciliation logic for future test improvements. [1] [2]timein test files to support new sleep functionality. [1] [2]