Closed yiqigao217 closed 3 years ago
Hi @adrianludwin this is ready for another review.
BTW since we now force adding excluded-namespaces labels to system namespaces in the e2e test, do I still need to change the testgrid? Is it using make test-e2e
target directly?
BTW since we now force adding excluded-namespaces labels to system namespaces in the e2e test, do I still need to change the testgrid? Is it using
make test-e2e
target directly?
hack/prow-run-e2e.sh
used in postsubmit and periodic e2e tests is using test-e2e
target, so no change is needed there.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: adrianludwin, yiqigao217
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Part of #1480
Force adding excluded-namespace labels to excluded namespaces before running the e2e test so that it won't break the cluster. E.g. HNC object webhook denies any object changes in namespaces without this label, it could break
kube-system
namespace if the label is missing.Add
test-e2e-batch
target and factor out the messages before e2e tests for regulartest-e2e
andtest-e2e-batch
. Add link to excluded-namespace concept.Tested by
make test-e2e
andmake test-e2e-batch N=3
.Prow config is unchanged because in
hack/prow-run-e2e.sh
for postsubmit and periodic e2e tests, it's already usingtest-e2e
target.The output for
make test-e2e-batch N=10
looks like this.