-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Simply k8s client configmap event reload it (7) #1425
Simply k8s client configmap event reload it (7) #1425
Conversation
…ly-k8s-client-catalog-watcher-it
…figmap-event-reload-it
@@ -625,10 +627,11 @@ private boolean isDeploymentReady(String deploymentName, String namespace) throw | |||
return availableReplicas != null && availableReplicas >= 1; | |||
} | |||
|
|||
private static void waitForDeploymentAfterPatch(String deploymentName, String namespace) { | |||
private static void waitForDeploymentAfterPatch(String deploymentName, String namespace, |
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.
this makes this method "stronger", meaning it makes it far more reliable in terms of knowing when it is safe to start assertions after a patch. I was forced to add labels in here and look for pods because I was having problems with tests
this PR goes in the same direction of changing the way we test via |
@ryanjbaxter one more refactor, things will get somehow more fun soon, when I remove integrations tests. Thank you |
No description provided.