fix: e2e readiness

Author: manusa

kubernetes-itests/src/test/java/io/fabric8/kubernetes/DeploymentIT.java

@@ -90,7 +90,7 @@ public void waitTest() {
     await().atMost(120, TimeUnit.SECONDS).until(deploymentReady);
     Deployment deploymentOne = client.apps().deployments()
       .inNamespace(session.getNamespace()).withName("deployment-wait").get();
-    assertTrue(Readiness.isDeploymentReady(deploymentOne));
+    assertTrue(Readiness.getInstance().isDeploymentReady(deploymentOne));
   }
 
   @Test

kubernetes-itests/src/test/java/io/fabric8/kubernetes/PodIT.java

@@ -166,7 +166,7 @@ public void evict() throws InterruptedException {
     // cant evict because only one left
     assertFalse(client.pods().inNamespace(session.getNamespace()).withName(pod1.getMetadata().getName()).evict());
     // ensure it really is still up
-    assertTrue(Readiness.isReady(client.pods().inNamespace(session.getNamespace()).withName(pod1.getMetadata().getName()).fromServer().get()));
+    assertTrue(Readiness.getInstance().isReady(client.pods().inNamespace(session.getNamespace()).withName(pod1.getMetadata().getName()).fromServer().get()));
 
     // create another pod to satisfy PDB
     client.pods().inNamespace(session.getNamespace()).createOrReplace(pod3);