When using custom network with IP-alias, use the former's subnet for the latter too #62172
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
k8s-ci-robot
added
release-note-none
|
/cc @wojtek-t |
shyamjvs
added
priority/critical-urgent
|
Added the priority labels as this is causing failures of our 100-node presubmit (though non-blocking) job. |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: shyamjvs, wojtek-t The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
|
Automatic merge from submit-queue (batch tested with PRs 62162, 60628, 62172). If you want to cherry-pick this change to another branch, please follow the instructions here. |
This was referenced Apr 6, 2018
k8s-github-robot
pushed a commit
that referenced
this pull request
Apr 6, 2018
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Fix IP-alias subnet creation logic Follows #62172 This fixes the failures happening when using ip-alias with custom network. The subnet name shouldn't be checked against the default value during creation, but just created if not present (as it's name can be different than default based on the value of `KUBE_GCE_IP_ALIAS_SUBNETWORK`). /cc @wojtek-t ```release-note NONE ```
|
Ref #62267 |
This was referenced Apr 19, 2018
k8s-github-robot
pushed a commit
that referenced
this pull request
Apr 19, 2018
#62193-#62398-upstream-release-1.10 Automatic merge from submit-queue. Automated cherry pick of #62172: When using custom network with IP-alias, use the former's #62193: Fix IP-alias subnet creation logic #62398: Fix subnet cleanup logic when using IP-aliases with custom Cherry pick of #62172 #62193 #62398 on release-1.10. #62172: When using custom network with IP-alias, use the former's #62193: Fix IP-alias subnet creation logic #62398: Fix subnet cleanup logic when using IP-aliases with custom ```release-note NONE ```
k8s-ci-robot
added
release-note
k8s-github-robot
pushed a commit
that referenced
this pull request
Apr 24, 2018
#62193-#62398-upstream-release-1.9 Automatic merge from submit-queue. Automated cherry pick of #62172: When using custom network with IP-alias, use the former's #62193: Fix IP-alias subnet creation logic #62398: Fix subnet cleanup logic when using IP-aliases with custom Cherry pick of #62172 #62193 #62398 on release-1.9. #62172: When using custom network with IP-alias, use the former's #62193: Fix IP-alias subnet creation logic #62398: Fix subnet cleanup logic when using IP-aliases with custom ```release-note Bugfixes allowing use of IP-aliases with custom-mode network in GCE setup scripts. ```
k8s-github-robot
pushed a commit
that referenced
this pull request
Apr 25, 2018
#62193-#62398-upstream-release-1.8 Automatic merge from submit-queue. Automated cherry pick of #62172: When using custom network with IP-alias, use the former's #62193: Fix IP-alias subnet creation logic #62398: Fix subnet cleanup logic when using IP-aliases with custom Cherry pick of #62172 #62193 #62398 on release-1.8. #62172: When using custom network with IP-alias, use the former's #62193: Fix IP-alias subnet creation logic #62398: Fix subnet cleanup logic when using IP-aliases with custom ```release-note Add support in GCE setup scripts to create cluster with custom network. Also bug-fixes to allow using custom network with IP-aliases. ```
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.
Currently, when we're using custom subnet and ip-alias simultaneously, the cluster fails to come up.
The reason is because we're creating a subnet in the former with one name, but expecting a differently named subnet for the latter.
This is causing continuous failures in our 100-node job where I recently turned both of them on.
cc @kubernetes/sig-network-bugs