-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle condition where minion cbr0 interface is up, but not yet readdressed, when vSphere script sets up cluster networking #31672
Conversation
Add additional logic to vSphere cluster quickstart script to handle situation where cbr0 interface is brought up but not immediately configured with the final subnet. Due to order of operations this would always occur with the highest numbered (ie. last to deploy) minion in the cluster. Previously the script would blindly push configuration for the default 172.18.0.0/16 subnet into the cluster, only for the cbr0 interface to eventually become reconfigured with the correct final subnet, breaking networking with containers deployed to that node. Also made the status messaging regarding the inter-node routing setup more verbose and added a missing newline.
Remove errant 'All rights reserved'.
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
8 similar comments
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
@zmerlynn I can verify this fix for you. Do you need any different help for this? |
I just haven't seen it in a while, sorry for the delay. @k8s-bot test this |
The CNCF CLA issue has to be resolved. You should squash the commits anyways, so if you fix the CLA issues and squash, it should tickle the bot. |
Jenkins GCI GKE smoke e2e failed for commit e55162e. Full PR test history. The magic incantation to run this job again is |
Jenkins GKE smoke e2e failed for commit e55162e. Full PR test history. The magic incantation to run this job again is |
Automatic merge from submit-queue vSphere kube-up: Wait for cbr0 configuration to complete before setting up routes. <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: Fixes routing setup when deploying via kube-up.sh on vSphere. Remove optimizations for salt status check till flakyness of install with optimization is addressed. **Which issue this PR fixes** fixes #34248, #31310 **Special notes for your reviewer**: Ref PR with a similar fix #31672
What this PR does / why we need it: Resolves bug reported in #31310
Which issue this PR fixes (optional, in
fixes #<issue number>(, #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #31310Special notes for your reviewer:
Release note:
NONE
This change is