test/e2e: Allow eventual consistency in deployment

Since the net-attach-def's deployment is not dependant on the deployment
of the net-attach-def's CRD (by Multus) - e2e test must allow for the
deployment to eventually settle before checking deployment.

Signed-off-by: Ram Lavi <[email protected]>

test/e2e/workflow/deployment_test.go

@@ -31,7 +31,7 @@ var _ = Describe("NetworkAddonsConfig", func() {
 				testConfigCreate(gvk, configSpec, components)
 
 				// Make sure that deployed components remain up and running
-				CheckConfigCondition(gvk, ConditionAvailable, ConditionTrue, CheckImmediately, time.Minute)
+				CheckConfigCondition(gvk, ConditionAvailable, ConditionTrue, 10*time.Second, time.Minute)
 			},
 			Entry(
 				"Empty config",
@@ -485,7 +485,7 @@ func checkConfigChange(gvk schema.GroupVersionKind, components []Component, whil
 		CheckConfigCondition(gvk, ConditionProgressing, ConditionTrue, 5*time.Minute, CheckDoNotRepeat)
 		// Wait until Available condition is reported. It may take a few minutes the first time
 		// we are pulling component images to the Node
-		CheckConfigCondition(gvk, ConditionAvailable, ConditionTrue, 15*time.Minute, CheckDoNotRepeat)
+		CheckConfigCondition(gvk, ConditionAvailable, ConditionTrue, 15*time.Minute, 10*time.Second)
 		CheckConfigCondition(gvk, ConditionProgressing, ConditionFalse, CheckImmediately, CheckDoNotRepeat)
 
 		// Check that all requested components have been deployed