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
feat(ci): remove minikube jobs and use multiple k3d jobs #3572
Conversation
1f6ae1e
to
745df90
Compare
Codecov Report
@@ Coverage Diff @@
## master #3572 +/- ##
==========================================
- Coverage 51.08% 51.06% -0.02%
==========================================
Files 925 925
Lines 56350 56350
==========================================
- Hits 28786 28776 -10
- Misses 25271 25284 +13
+ Partials 2293 2290 -3
Continue to review full report at Codecov.
|
beb88c9
to
bf69528
Compare
Run against minimum and maximum supported k8s version in a k3d job This enables us to get rid of minikube jobs Signed-off-by: Charly Molter <charly.molter@konghq.com>
we now handle case where KIND_CLUSTER_NAME is not set Signed-off-by: Charly Molter <charly.molter@konghq.com>
They are not providing a lot of value Signed-off-by: Charly Molter <charly.molter@konghq.com>
Signed-off-by: Charly Molter <charly.molter@konghq.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
finally!
Please also remember about removing related makefiles
Run against minimum and maximum supported k8s version in a k3d job
This enables us to get rid of minikube jobs
Signed-off-by: Charly Molter charly.molter@konghq.com
Summary
SUMMARY_GOES_HERE
Full changelog
Issues resolved
Fix #3642
Fix #3245
Documentation
Testing
Backwards compatibility
UPGRADE.md
with any steps users will need to takewhen upgrading.
backport-to-stable
label if the code is backwards compatible. Otherwise, list breaking changes.