Improve tests section, remove TODO
@@ -438,8 +438,21 @@ None that I can think of at the moment
### Test Plan
+#### General tests
+
- Add unit tests to the Cluster Ingress Operator to make sure the
-IngressController resource is generated as exepected.
+IngressController resource and corresponding Deployment is generated as
+exepected.
+
+- Add tests on both cloud / "none"-platform that check that a single-node cluster
+with additional workers recovers after the single control-plane node reboots by
+running conformance tests post-reboot.
+
+- Add tests on both cloud / "none"-platform that check that a single-node cluster
+with additional workers recovers after an upgrade by running conformance tests
+post-upgrade.
+
+#### Day-2 workers tests
- Add periodic nightly tests which install single-node in the cloud, add a few
worker nodes to it, then run conformance tests to make sure we don't run into
@@ -448,17 +461,17 @@ any problems not described in this enhancement.
- Add periodic nightly tests which install a single-node "none"-platform cluster,
add worker nodes to it, and check that ingress traffic still works as expected
and recovers even after the `router-default` pod gets deleted and rescheduled.
-Make sure this is still true even after upgrades.
-- Add tests on both cloud / "none"-platform that check that a single-node cluster
-with additional workers recovers after the single control-plane node reboots by
-running conformance tests post-reboot.
+#### Day-1 workers tests
-- Add tests on both cloud / "none"-platform that check that a single-node cluster
-with additional workers recovers after an upgrade by running conformance tests
-post-upgrade.
+- Add periodic nightly tests which install a single control-plane node cluster
+with a few additional workers in the cloud, then run conformance tests to make
+sure we don't run into any problems not described in this enhancement.
-TODO: Describe day-1-workers tests?
+- Add periodic nightly tests which install a single control-plane "none"-platform
+cluster with additional workers and check that ingress traffic still works as
+expected and recovers even after the `router-default` pod gets deleted and
+rescheduled.
### Graduation Criteria
