Configure Service Accounts for Pods page doesn't talk about the new BoundServiceAccountTokenVolume feature

[fasaxc]

This is a Bug Report

Problem:
Configure Service Accounts for Pods page doesn't talk about the new BoundServiceAccountTokenVolume feature, it describes time-based expiration but tokens can now expire for other reasons.

Proposed Solution:
Add note about BoundServiceAccountTokenVolume and that it means that service account tokens are now revoked on pod termination.

Page to Update:
https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/

v1.21+

[fasaxc]

/sig auth
@liggitt

[liggitt]

https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection refers to these tokens

[liggitt]

The service account token will also become invalid against the API when the Pod or the ServiceAccount is deleted.

[sftim]

I agree, the docs do mention ServiceAccount token volume projection.

It would be nice to have a concept page about ServiceAccounts (see #31847); the task pages could then refer people to that concept page for further reading.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[ritazh]

/triage accepted
/remove-lifecycle rotten