[2.12.x] chore: upgrade KTF and pin Kuma to 2.6.2 #5760
Conversation
|
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/8458441457 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release/2.12.x #5760 +/- ##
==============================================
Coverage 68.0% 68.0%
==============================================
Files 165 165
Lines 19344 19352 +8
==============================================
+ Hits 13159 13168 +9
Misses 5397 5397
+ Partials 788 787 -1 ☔ View full report in Codecov by Sentry. |
|
We still need to pin the kuma version because without version, kuma addon in KTF could not recognize the version and cannot configure the |
Set the Kuma version and use a more modern addon builder. Currently uses an unreleased KTF version.
rainest
force-pushed
the
chore/ktf-backport
branch
from
676ea73
to
a913d9c
Compare
rainest
added
size/XS
ci/run-e2e
|
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/8471491584 |
* set appProtocol to HTTP for kuma tests * Update test/e2e/helpers_test.go Co-authored-by: Grzegorz Burzyński <czeslavo@gmail.com> --------- Co-authored-by: Grzegorz Burzyński <czeslavo@gmail.com>
|
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/8473225109 |
|
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/8479837105 |
pmalek
changed the title
Updates KTF to 0.39.2. Draft pending actual release of that.
Pins the 2.12.x Kuma test version to 2.6.2 (essentially arbitrary, it's just the current version used in main). main currently manages this via Renovate, but the 2.12.x branch does not have Renovate set up. Doing so is possible (https://docs.renovatebot.com/configuration-options/#basebranches allows updating more than one branch) at the cost of some additional setup and maintenance, though we generally don't provide any guarantees of forward compatibility for LTS KIC, so IDK if we'd want to bother.
Backports #5507 for the same reason we originally did that.