Conversation
|
//usebom:sandbox/v1.7.0-zshippable/431703182511446831/tkg-compatibility:v12 |
5ac0f1e to
3fab37c
Compare
|
Cluster Generation A/B Results: |
Codecov Report
@@ Coverage Diff @@
## main #3772 +/- ##
==========================================
- Coverage 46.58% 45.69% -0.89%
==========================================
Files 400 425 +25
Lines 39722 41278 +1556
==========================================
+ Hits 18504 18863 +359
- Misses 19519 20700 +1181
- Partials 1699 1715 +16
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Signed-off-by: Sagar Muchhal <[email protected]>
Signed-off-by: Ashutosh Kumar <[email protected]>
Signed-off-by: Ashutosh Kumar <[email protected]>
This patch changes the overlays to include the customization of the subnets for cluster creation only when using a custom VPC. The overlays now check for the presence of the VPC ID and the public/private subnet ID, before including those blocks for cluster YAML creation. Since, the public/private subnets can be used only when using a custom VPC. Otherwise we leave the AWSCluster.spec.network.subnets slice empty and let CAPA handle the creation of the resources. Signed-off-by: Sagar Muchhal <[email protected]>
3fab37c to
80b89f4
Compare
|
Cluster Generation A/B Results: |
|
Cluster Generation A/B Results: |
3d86c51 to
6285a86
Compare
|
Cluster Generation A/B Results: |
6285a86 to
006af5a
Compare
|
Cluster Generation A/B Results: |
* Bump CAPI to v1.2.3 * Bump CAPA to v2.0.0-beta.1 (v1beta2) * Bump CAPV to v1.4.1 Signed-off-by: Sagar Muchhal <[email protected]> * update go modules * bump capz to v1.5.2 Signed-off-by: Ashutosh Kumar <[email protected]> * update CAPI yamls to v1.2.4 * update CAPI go deps to v1.2.4 * bump capz to v1.5.3 Signed-off-by: Ashutosh Kumar <[email protected]> * fix packages * update UT with new aws IAM * modify AWS provider * rename provider of aws and vsphere to pickup changes * revert folder name back to latest ones * Fixes custom AWS VPC configuration This patch changes the overlays to include the customization of the subnets for cluster creation only when using a custom VPC. The overlays now check for the presence of the VPC ID and the public/private subnet ID, before including those blocks for cluster YAML creation. Since, the public/private subnets can be used only when using a custom VPC. Otherwise we leave the AWSCluster.spec.network.subnets slice empty and let CAPA handle the creation of the resources. Signed-off-by: Sagar Muchhal <[email protected]> * update go.mod and go.sum after rebase Signed-off-by: Sagar Muchhal <[email protected]> Signed-off-by: Ashutosh Kumar <[email protected]> Co-authored-by: Yuvaraj Kakaraparthi <[email protected]> Co-authored-by: Sedef Savas <[email protected]> Co-authored-by: Sagar Muchhal <[email protected]> Co-authored-by: Ashutosh Kumar <[email protected]>
|
@jeffwubj please follow the PR template and provide some details on what the change is about, what tests were run, etc. |
hi @vuil : description updated. this is not temporary but the CAP* bump PR, I have re-run all tests in #3604 to see the latest status, seems all pipelines are still passed, feel free to let me know if anything has been found |
What this PR does / why we need it
Which issue(s) this PR fixes
Fixes #
Bump Cluster API and providers, forked from #3699 with pipeline fix
Describe testing done for PR
Release note
Additional information
Special notes for your reviewer