fix(publick8s) specify pod subnets explicitly #431
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: Damien Duportal <damien.duportal@gmail.com>
dduportal
force-pushed
the
fix/publick8s/pod-subnets
branch
from
1f74f01
to
7f256eb
Compare
dduportal
changed the title
|
Without this, pods were allocated an IP in the "public" vnet but not specifically in the "publick8s-tier" subnet. (Some were in 10.244.x.x like the accountapp, which prevented it to access the ldap due to ldap loadBalancerSourceRanges not including it) |
|
Ref.
=> this attribute was introduced after our initial creation of the cluster |
lemeurherve
approved these changes
Jul 7, 2023
dduportal
commented
Jul 7, 2023
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.
Ref. jenkins-infra/helpdesk#3582 (comment)