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
The success or failure of a deploy is currently measured by whether the kubectl apply command successfully. This can lead to a situation where the deploy status reads as successful, but the app isn't properly updated in kubernetes. This has happened a couple times as the result of an ImagePullBackOff error, for instance.
It would probably be more useful to check AKS for a new pod in that deployment and check its status instead, so if the apply succeeds but the provisioning fails, there's a red notification.
The text was updated successfully, but these errors were encountered:
The success or failure of a deploy is currently measured by whether the
kubectl apply
command successfully. This can lead to a situation where the deploy status reads as successful, but the app isn't properly updated in kubernetes. This has happened a couple times as the result of an ImagePullBackOff error, for instance.It would probably be more useful to check AKS for a new pod in that deployment and check its status instead, so if the apply succeeds but the provisioning fails, there's a red notification.
The text was updated successfully, but these errors were encountered: