So I actually tracked down the Issue, apparently in a previous Kubernetes version they deprecated the serviceaccount syntax and changed it to serviceaccountname using the version of Kubernetes we use locally it does not seem to support this new field name.
Not a bug just API version deprecation's and pain for those of us that don't follow the bleeding edge. hopefully this helps someone else out there.