-
Notifications
You must be signed in to change notification settings - Fork 594
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
use namespace kong for integration tests #4439
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #4439 +/- ##
=======================================
- Coverage 67.9% 67.8% -0.2%
=======================================
Files 161 161
Lines 18817 18817
=======================================
- Hits 12788 12764 -24
- Misses 5270 5296 +26
+ Partials 759 757 -2 ☔ View full report in Codecov by Sentry. |
59db41d
to
59eb210
Compare
blocked by Kong/kubernetes-testing-framework#765 |
59eb210
to
020b873
Compare
020b873
to
17a7ad2
Compare
17a7ad2
to
048dd9c
Compare
Integration (targeted) tests with KIND-based cluster and latest images were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/5806095248 |
What this PR does / why we need it:
use namespace
kong
instead ofkong-system
for integration tests, and change the hard coded namespacekong-system
toconst.ControllerNamespace
.Which issue this PR fixes:
fixes #4431
Special notes for your reviewer:
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR