fix: kubeconfig not found

[fredleger]

Description

Which issue # does this fix? And was it approved before you worked on it?

Checklist:

• [x] Fixes issue: #44
• [ ] I waited for approval before creating this PR

Note: if the PR is for a typo, please close it and raise an issue instead.

Are you a GitHub Sponsor (Yes/No?)

Pull Requests from sponsors get prioritised and a quicker response.

Check at: https://github.com/sponsors/alexellis

• [ ] Yes
• [x] No

How Has This Been Tested?

• Forked repo
• added automountServiceAccountToken: true
• used the forked repo in argocd to deploy to 3 clusters in 1.23
• checked that it fixed the error (and of course it did)

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

• [x] updated the documentation and/or roadmap (if required)
• [x] read the CONTRIBUTION guide
• [x] signed-off my commits with git commit -s
• [x] added unit tests

[derek[bot]]

Thank you for your contribution. unfortunately, one or more of your commits are missing the required "Signed-off-by:" statement. Signing off is part of the Developer Certificate of Origin (DCO) which is used by this project.

Read the DCO and project contributing guide carefully, and amend your commits using the git CLI. Note that this does not require any cryptography, keys or special steps to be taken.

:bulb: Shall we fix this?

This will only take a few moments.

First, clone your fork and checkout this branch using the git CLI.

Next, set up your real name and email address:

git config --global user.name "Your Full Name" git config --global user.email "you@domain.com"

Finally, run one of these commands to add the "Signed-off-by" line to your commits.

If you only have one commit so far then run: git commit --amend --signoff and then git push --force. If you have multiple commits, watch this video.

Check that the message has been added properly by running "git log".

[alexellis]

I haven't run into this problem, but don't use the tool myself. I'll take it from you that you've tested this and that it fixes your issues for your company.

Do you need a release?

[fredleger]

thanks @alexellis i confirm it's in production for a week now on 3 clusters and it does work would be nice in order to have a clear tag on the history instead of a commit id.

thanks for the great work