-
Notifications
You must be signed in to change notification settings - Fork 305
Use Path.DirectorySeparatorChar
to have ServiceAccountPath start from root
#342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Path.DirectorySeparatorChar
to have ServiceAccountPath start from root
#342
Conversation
…om root, instead of a relative path. This should work fine on Linux containers, but it still assumes the Windows container working drive is "C:"
Welcome @darobs! |
do you mean |
In Windows, this pathname resolves to Example:
So this PR works fine if the current working directory in the Windows container is on the same drive as |
@darobs IHMO, we need to find out a Windows way to do so. |
/lgtm Regardless of windows or not this is an improvement on the current code. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brendandburns, darobs 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:
Approvers can indicate their approval by writing |
The path constructed in
KubernetesClientConfiguration::ServiceAccountPath
is a relative path, and this works fine as long as CWD is the root directory.This PR uses
Path.DirectorySeparatorChar
to haveServiceAccountPath
start from root, instead of a relative path.This should work fine on Linux containers, but it still assumes the Windows container working drive is "C:"