fix(ci): render infra config#2223
Merged
Merged
Conversation
Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
6e2725a to
d468cde
Compare
nevermarine
approved these changes
Apr 16, 2026
diafour
approved these changes
Apr 16, 2026
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.
Description
Fixes the infrastructure configuration rendering for nested e2e clusters by correcting the YAML structure and the Helm template lookup logic.
Changes:
e2e-reusable-pipeline.yml- movednetworkConfigto the correct nesting level_helpers.tplto properly extractnetworkConfigfrom theinstancesvalues usinggetfunction instead of incorrectdigcallWhy do we need it, and what problem does it solve?
The previous implementation (#2181) introduced SDN configuration for nested e2e clusters, but the YAML structure was incorrectly nested and the Helm template was unable to properly access the
networkConfigvalues. This caused theclusterNetworkNameto be empty, preventing VMs from connecting to the configured ClusterNetwork.What is the expected result?
networkConfigblock is correctly rendered in the infra values YAMLnetworkConfig.clusterNetworkNamefrom instancesChecklist
Changelog entries