This message was deleted.
# general
s
This message was deleted.
w
I suspect this is a different issue - but also something we should look at. I think this is related to using the
waitForReady
setting, which waits for the container to report healthy, which may take some time after the container is initially registered while the containers spin up. cc @lemon-spoon-91807