fix: correctly inject podNetwork cidr in cp chart values
#763
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
gardener-robot
added
needs/review
gardener-robot-ci-2
added
reviewed/ok-to-test
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.
How to categorize this PR?
/area networking
/kind bug
/platform alicloud
What this PR does / why we need it:
Fix wrongly introduced
podNetworkinjection from g/g update in #746.Else, it gets injected as
[10.251.0.0/16], which cannot be parsed:sync route tables error: sync table [...] error: error parse cluster cidr [10.251.0.0/16]: invalid CIDR address: [10.251.0.0/16].With this fix, it's working now:
sync route tables successfully, tables [...].v1.57.x.Special notes for your reviewer:
/cc @MartinWeindel
Release note: