remove ipv6 workaround from post kubeadm#3765
Conversation
|
Cluster Generation A/B Results: |
Codecov Report
@@ Coverage Diff @@
## main #3765 +/- ##
==========================================
- Coverage 46.60% 45.71% -0.90%
==========================================
Files 400 425 +25
Lines 39726 41282 +1556
==========================================
+ Hits 18516 18873 +357
- Misses 19513 20695 +1182
- Partials 1697 1714 +17
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
question: Does this only apply to vsphere? |
|
Yes, we only support ipv6 on vsphere at the moment. |
tenczar
left a comment
There was a problem hiding this comment.
This will need to be rebased because of the providers bump, but looks good so far. Do we want to remove this hack from the legacy overlays as well?
DanielXiao
left a comment
There was a problem hiding this comment.
Can you rebase this PR? There is a folder name change in #3772
all current versions of tanzu are using a new-enough version of containerd (v1.5.0 or greater) that we can remove this workaround the issue this addressed was fixed in containerd/containerd#5145 Signed-off-by: Aidan Obley <[email protected]> Co-authored-by: Christian Ang <[email protected]>
5ab49cb to
80ab92b
Compare
|
Cluster Generation A/B Results: |
What this PR does / why we need it
all current versions of tanzu are using a new-enough version of containerd (v1.5.0 or greater) that we can remove this workaround
the issue this addressed was fixed in
containerd/containerd#5145
Describe testing done for PR
Created a cluster to verify it comes up without this workaround
Release note
Additional information
Special notes for your reviewer