-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Remove certmanager integration tests #15261
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15261 +/- ##
=======================================
Coverage 84.76% 84.76%
=======================================
Files 218 218
Lines 13479 13479
=======================================
+ Hits 11425 11426 +1
- Misses 1686 1687 +1
+ Partials 368 366 -2 ☔ View full report in Codecov by Sentry. |
/assign @ReToCode |
Next steps:
|
Hm, can we just run them on "Serving"? I don't think we need a separate job that runs the "same" as we already have in Serving. Or am I missing something? |
That will happen after the clean up, I don't plan to run them in a separate one but I want also to understand if we are going to test with those signers or not (we will run only with the ca one?). I want also to make sure tests are running ok first. I will do the follow up PRs. |
test/e2e/certmanager/e2e-tests.sh
Outdated
add_trap "kubectl delete -f ./test/e2e/certmanager/config/autotls/certmanager/http01/ --ignore-not-found" SIGKILL SIGTERM SIGQUIT | ||
go_test_e2e -timeout=10m ./test/e2e/certmanager/conformance \ | ||
-run TestHTTP01Conformance \ | ||
"--certificateClass=${CERTIFICATE_CLASS}" || fail_test | ||
kubectl delete -f ./test/e2e/certmanager/config/autotls/certmanager/http01/ | ||
kubectl delete -f "${E2E_YAML_DIR}"/test/config/externaldomaintls/certmanager/http01/ |
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.
Do we need both mesh and the other issuer for http01? cc @ReToCode
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.
Mesh? Each test has its own issuer, if this is what you are asking?
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.
There are two files https://github.com/knative-extensions/net-certmanager/blob/main/test/config/autotls/certmanager/http01/issuer.yaml
https://github.com/knative-extensions/net-certmanager/blob/main/test/config/autotls/certmanager/http01/mesh-issuer.yaml
When we apply the resources under http01 dir both are applied should we merge?
Although tests pass I see:
Error from server (NotFound): error when deleting "/tmp/knative.aB6zlpVa/ci-2024-05-27-21-25-25-2PDN6eysqT/e2e-yaml/test/config/externaldomaintls/certmanager/http01/mesh-issuer.yaml": clusterissuers.cert-manager.io "http01-issuer" not found
/lgtm |
/hold |
/unhold |
/hold |
Holding for knative/infra#447, then I will remove the tests here. cc @dprotaso |
you'll have to run codegen - some stuff in vendor will be pruned |
baf3ded
to
1ac5bff
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, skonto The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
Fixes #15266
Proposed Changes
We dont need the tests.
Release Note