-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Unable to connect cluster when specified executor.serviceAccountName
but autoMountServiceAccountToken: false
#10937
Comments
Related Discussion: #10885 |
I think I've figured out why: The main container didn't mount the |
Would you like to submit a PR to fix it? |
@terrytangyuan 👍 Please assign this issue to me. |
…isabled. Fixes argoproj#10937 (argoproj#10945) Signed-off-by: Dillen Padhiar <dillen_padhiar@intuit.com>
serviceAccountName
but autoMountServiceAccountToken: false
Per #12848 (comment), this seems to have been incorrectly analyzed: an SA token shouldn't be mounted to the |
serviceAccountName
but autoMountServiceAccountToken: false
executor.serviceAccountName
but autoMountServiceAccountToken: false
Pre-requisites
:latest
What happened/what you expected to happen?
What happened
Occurred below errors while creating resource via container/script template
what you expected to happen?
Able to create resource via container/script template successfully.
Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: