This message was deleted.

For future reference, the issue turned out to be due to the presence of "automountServiceAccountToken: false" in service account spec.