We have tests in our startup scripts to determine whether the service accounts have sufficient permissions for kube ping to work however the kube ping code continues to assume access and logs failures on the console.
A better way to handle this would be to suppress error messages until we have succeeded, i.e. while we expect failures to occur we should not pollute the logs until we have successfully queried kube ping. After a success we can then display errors.
This impacts all A-MQ/EAP based images.