This message was deleted.

This appears to be the result of a bug in the recent release of the nginx ingress controller.