You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing tests it's useful to figure why a pod failed to start.
For example we use heavily terratest in our e2e suite on kumahq/kuma.
Some tests are flaky for many possible reasons. When investigating them we have to switch to using: WaitUntilPodAvailableE and use the error to get the pod again to extract the status. Something like:
When writing tests it's useful to figure why a pod failed to start.
For example we use heavily terratest in our e2e suite on kumahq/kuma.
Some tests are flaky for many possible reasons. When investigating them we have to switch to using:
WaitUntilPodAvailableE
and use the error to get the pod again to extract the status. Something like:Not only there's a race here (possibly the pod gets healthy right after failing but it's also not super easy.
2 options:
pod.Status.{Reason,Message}
toPodNotAvailable
errorPodNotAvailable
accessible outside the package.I have a preference for 1.
The text was updated successfully, but these errors were encountered: