Skip to content
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

Enable Linkerd proxy injection to work without "automountServiceAccountToken" set to true #6862

Closed
HighWatersDev opened this issue Sep 10, 2021 · 2 comments

Comments

@HighWatersDev
Copy link

Feature Request

Enable Linkerd to inject proxy without needing automountServiceAccountToken set to true for mTLS.

What problem are you trying to solve?

By default automountServiceAccountToken is set to false. This is also recommended setting in certain environments.

How should the problem be solved?

One of the proposed solutions is to use token volume projection ref.

The other possible solution is to use admission controller as implemented by some other mesh services.

What do you want to happen? Add any considered drawbacks.

Alternative method of injecting proxy sidecar for mTLS without using service account token automount option.

Previously discussed in this issue: #4651

@olix0r olix0r added help wanted area/injector area/identity Automatic transport identity labels Sep 13, 2021
@olix0r olix0r added this to the stable-2.12.0 milestone Sep 13, 2021
@snoord
Copy link

snoord commented Nov 4, 2021

I think this is resolved by #7117

@olix0r
Copy link
Member

olix0r commented Nov 4, 2021

@snoord I think you're correct. It would be good to add a test that checks that a pod with automountServiceAccounToken: false becomes ready

@olix0r olix0r added the priority/P1 Planned for Release label Jan 21, 2022
@alpeb alpeb self-assigned this Feb 11, 2022
@olix0r olix0r unassigned alpeb Jun 9, 2022
@adleong adleong removed this from the stable-2.12.0 milestone Aug 4, 2022
@olix0r olix0r closed this as completed Mar 3, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants