This message was deleted.

It turned out to be an issue with a pod that needed to be restarted. I wasn't sure if the pod could have been deleted as I wasn't aware it had a deployment behind it.