Fix k8s node join time not enough issue#20141
Merged
wangxin merged 2 commits intosonic-net:masterfrom Aug 11, 2025
Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
wangxin
approved these changes
Aug 10, 2025
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Aug 11, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes.
Collaborator
|
Cherry-pick PR to 202411: #20173 |
11 tasks
Collaborator
|
Cherry-pick PR to 202505: #20176 |
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Aug 11, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes.
11 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Aug 12, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes.
mssonicbld
added
Included in 202505 branch
and removed
Created PR to 202505 branch
labels
mssonicbld
pushed a commit
that referenced
this pull request
Aug 12, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes.
mssonicbld
added
Included in 202411 branch
and removed
Created PR to 202411 branch
labels
ashutosh-agrawal
pushed a commit
to ashutosh-agrawal/sonic-mgmt
that referenced
this pull request
Aug 14, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes.
vidyac86
pushed a commit
to vidyac86/sonic-mgmt
that referenced
this pull request
Oct 23, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes.
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes. Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes. Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes.
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes. Signed-off-by: Yael Tzur <ytzur@nvidia.com>
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
Signed-off-by: Nazarii Hnydyn nazariig@nvidia.com A new SKU for MSN4600C platform: Mellanox-SN4600C-D24C52 Requirements for Mellanox-SN4600C-D24C52: 8 x 100Gbps uplink to T2 switch (C25, C26, C29-C30, C33-C34, C37-C38) 12 x 100Gbps downlinks to T0 switch (C1-C2, C3-C4, C7-C8, C53-C54, C57-C58, C63-C64) 1 x 50Gbps downlinks to T0 switch (D62) Type of transceiver: "100Gb AOC between T0-T1, 100G DAC between T0-Server" Cable length: “T0-T1 40m default, 300m max; T0-Server 2m” Breakout mode: "per port layout" FEC mode: "none" VxLAN source port: "no" Static Policy Based Hashing: "no" Traditional buffer model: "yes" Shared headroom: “yes” Over-subscription ratio: “2” Warm boot: “yes” Additional details: Mellanox-SN4600C-D24C52 is a replacement for Mellanox-SN3800-D24C52 Why I did it Added Mellanox-SN4600C-D24C52 to replace Mellanox-SN3800-D24C52 Work item tracking N/A How I did it Added relevant configuration files How to verify it Generate port configuration: sonic-cfggen -H -k Mellanox-SN4600C-D24C52 --preset t1 > /etc/sonic/config_db.json Generate QoS configuration: config qos clear config qos reload --no-dynamic-buffer config save -y Details if related Backport from master: [Mellanox]: Add Mellanox-SN4600C-D24C52 SKU sonic-net#20142
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
What is the motivation for this PR? It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster. How did you do it? Increased the wait time for joining node to cluster. How did you verify/test it? Run this test in testbed vms75-t0-7050cx3-1 to see if it passes.
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
6 participants
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 of PR
Summary: It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster, so increased the wait time for joining node to cluster.
Fixes # (33976122)
Type of change
Back port request
Approach
What is the motivation for this PR?
It's an improvement for testbed vms75-t0-7050cx3-1. For this SKU, the kubelet needs more time(around 70s) to join the minikube cluster.
How did you do it?
Increased the wait time for joining node to cluster.
How did you verify/test it?
Run this test in testbed vms75-t0-7050cx3-1 to see if it passes.
Any platform specific information?
None
Supported testbed topology if it's a new test case?
None
Documentation