Remove check for serviceaccount and namespace being *

[logandavies181]

Since #48 (#53) we're able to sensibly allow all serviceaccounts in all namespaces to authenticate to Vault, for example mapping them to a templated policy.
Since #58 we're able to get around the check by doing this:

vault write auth/kubernetes/role/myrole \
bound_service_account_names=a*,b*,c*,d*,e*,f*,h*,i*,j*,k*,l*,m*,n*,o*,p*,q*,r*,s*,t*,u*,v*,w*,x*,y*,z*,1*,2*,3*,4*,5*,6*,7*,8*,9*,0* \ 
bound_service_account_namespaces=* policies=my_templated_policy

This PR is to remove the now unnecessary check for bound_service_account_name and bound_service_account_namespace being *

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

1 out of 2 committers have signed the CLA.

• logandavies181
• daviesl2

---

daviesl2 seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[james-atwill-hs]

This is outstanding to finally resolve #47 .. is there a way to move this along?

[buckner]

Any chance this could get looked at? @logandavies181

[tyrannosaurus-becks]

Closing due to inactivity and to lack of signing the contributor agreement. However, I do still think this is an important request and will either submit a similar PR or will chat with folks about it further on #47.