feat: custom path for service account token (supporting TokenVolume projection)

[omerlh]

fix #1528

I am not sure about the CA - I need to see if it will be there if using the projected volume 🤔

[k8s-ci-robot]

Welcome @omerlh!

It looks like this is your first PR to kubernetes-client/javascript 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/javascript has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[omerlh]

While investigating the issue with CA and token projection I found this issue kubernetes/kubernetes#53315, I asked for help on Kubernetes slack

[omerlh]

When using TokenProjection need also to mount the custom config map kube-root-ca.crt with the API server CA certificate so I add the option to specify path to the CA as well

[brendandburns]

/lgtm
/approve

Thanks for the PR!

Once this merges, can you cherrypick it into the release-1.x branch also?

[brendandburns]

ugh, looks like we need to fix the linter somewhat.

[omerlh]

Yeah, the linter error does not look related to my changes so I am not sure what to do, I think need to upgrade linter rules maybe?

[mstruebing]

Hey @omerlh I think the linter errors are not really failing, prettier is what is failing.
If I run npm run format and after that npm run lint I get an exit code of zero.
Without running npm run format it's 1. So if you run npm run format and commit and push these changes the linter should be satisfied.

I'm not sure about our linter setup though, we should probably switch to eslint or something else which is supported as tslint is deprecated since quite a while (2019)

[omerlh]

Sure, I just did - let's see if this will help!

[mstruebing]

/lgtm
/approve

Thank you for your contribution 🎉

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns, mstruebing, omerlh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [brendandburns,mstruebing]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment