Kops Docs: Fix ServiceAccountVolume proposed configuration

[dntosas]

Seems that after merging kubernetes/kops#9534 there is no need to specify paths for key-files for service Account Token Volume Projection.

Instead, current configuration proposed is making Istio unable to verify JWT token with errors.

2021-02-01T22:05:23.240319Z     error   ads     Failed to authenticate client from x.x.x.x
Authenticator ClientCertAuthenticator: no verified chain is found
; Authenticator KubeJWTAuthenticator: failed to validate the JWT from cluster Kubernetes: the service account authentication returns an error: [invalid bearer token, square/go-jose: error in cryptographic primitive, unknown]

In this commit, we remove the paths, letting Kops handles the default ones that are working as expected.

Relevant PR also opened at Kops repo kubernetes/kops#10712

[x] Configuration Infrastructure
[x] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[ ] Developer Infrastructure

[istio-policy-bot]

😊 Welcome! This is either your first contribution to the Istio documentation repo, or
it's been awhile since you've been here. A few things you should know:

• You can learn about how we write and maintain documentation, about our style guidelines,
  and about all the available web site features by visiting Contributing to the Docs.

• In the next few minutes, an automatic preview of your change will be
  built as a full copy of the istio.io website. You can find this preview by clicking on
  the Details link next to the deploy/netlify entry in the Status section of this
  page.

• We care about quality, so we've put in place a number of checks to ensure our documentation
  is top notch. We do spell checking, we sanitize the markdown, we ensure all hyperlinks point
  to valid location, and more. If your PR doesn't pass one of these checks, you'll see a red X in the
  status section of the page. Click on the Details link to get a list of the problems with your PR.
  Fix those problems and push an update to your PR. This will automatically rerun the tests and
  hopefully this time everything will be perfect.

• Once your changes are accepted and merged into the repository, they will initially show up
  on https://preliminary.istio.io. The changes will be published to https://istio.io
  the next time we do a major release (which typically happens every 3 months or so).

Thanks for contributing!

Courtesy of your friendly welcome wagon.

[istio-testing]

Hi @dntosas. Thanks for your PR.

I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ericvn]

Leaving these items as 1. lets them be renumbered automatically as other items are added in the middle.

[dntosas]

thanx for catching this ^^ pushed changes

[ericvn]

/ok-to-test

[dntosas]

/retest

Changes made

[istio-testing]

@dntosas: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
doc.test.profile_none_istio.io	33ecc88	link	/test doc.test.profile_none_istio.io
doc.test.profile_default_istio.io	33ecc88	link	/test doc.test.profile_default_istio.io

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.