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

Whats the impact of removing the auto mount of access token for cert manager service accounts. #5881

Closed
ghost opened this issue Mar 23, 2023 · 7 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@ghost
Copy link

ghost commented Mar 23, 2023

I have deployed the cert manager on aks, but microsoft inbuilt cloud defender security raised the high severity vulnerability on auto mount of access tokens for service accounts.

I would like to know on the following items:

Does cert manager supports disabling automount of sa tokens. if not , is it on future roadmap.
What will be the impact of mounting the tokens manually but on different mounted path.

@ghost
Copy link
Author

ghost commented Mar 27, 2023

any updates on this ?

@spikepanx
Copy link

... have a look into the best practices.
But, imho, this only works for the controller pod. cainjector, webhook, etc. do not have related templating in the Deployment templates. Don't know if this is by intention and only the docs are not up-to-date

@druesendieb
Copy link

... have a look into the best practices. But, imho, this only works for the controller pod. cainjector, webhook, etc. do not have related templating in the Deployment templates. Don't know if this is by intention and only the docs are not up-to-date

I just stumbled upon the same issue. This will be fixed in 1.12.0, see release notes and #5668

@jetstack-bot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

@jetstack-bot jetstack-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 20, 2023
@jetstack-bot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

@jetstack-bot jetstack-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 19, 2023
@jetstack-bot
Copy link
Collaborator

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

@jetstack-bot
Copy link
Collaborator

@jetstack-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants