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 using infrastructure as code in a DevOps pipeline my K8s cluster is created and I then run dapr init and helm install (of my application) if you do that too quickly no side cars will be injected into my pods because the dapr containers are still being created.
This required me to write custom logic to repeatedly calling dapr status and checking if I found the word false or not. This works but makes my pipeline fragile. If the output of dapr status were to change my pipeline would fail.
If dapr init and dapr upgrade offered a --wait flag that would cause the call to block until all the containers are healthy would eliminate the need for customer implementations of waiting logic.
Release Note
RELEASE NOTE: ADDED--wait flag for init and upgrade commands
The text was updated successfully, but these errors were encountered:
Describe the proposal
When using infrastructure as code in a DevOps pipeline my K8s cluster is created and I then run dapr init and helm install (of my application) if you do that too quickly no side cars will be injected into my pods because the dapr containers are still being created.
This required me to write custom logic to repeatedly calling dapr status and checking if I found the word
false
or not. This works but makes my pipeline fragile. If the output of dapr status were to change my pipeline would fail.If dapr init and dapr upgrade offered a --wait flag that would cause the call to block until all the containers are healthy would eliminate the need for customer implementations of waiting logic.
Release Note
RELEASE NOTE: ADDED
--wait
flag forinit
andupgrade
commandsThe text was updated successfully, but these errors were encountered: