labels.purgeUserInfoDay=刪除以前的使用者日誌
labels.reading=讀音
labels.roleTypeIds=角色ID
labels.scriptData=腳本
labels.scriptResult=結果
labels.scriptType=執行方法
labels.segmentation=分段
labels.startTime=開始時間
labels.target=目標
labels.token=令牌
labels.synonymFile=同義詞檔案
labels.stopwordsFile=停用詞檔案
labels.stemmerOverrideFile=詞幹覆蓋檔案
labels.mappingFile=映射檔案
labels.protwordsFile=Protwords檔案
labels.kuromojiFile=Kuromoji檔案
labels.elevateWordFile=提升詞檔案

* Google Compute Engine PD Detach fails if node no longer exists ([29358](https://github.com/kubernetes/kubernetes/issues/29358))
* Mounting (only 'default-token') volume takes a long time when creating a batch of pods  (parallelization issue) ([28616](https://github.com/kubernetes/kubernetes/issues/28616))

`get_current_user` 함수를 이전과 동일한 토큰을 받도록 수정하되, 이번에는 JWT 토큰을 사용하도록 합니다.

받은 토큰을 디코딩하여 검증한 후 현재 사용자를 반환합니다.

토큰이 유효하지 않다면 HTTP 오류를 반환합니다.

{* ../../docs_src/security/tutorial004_an_py310.py hl[90:107] *}

## `/token` 경로 작업 수정

토큰의 만료 시각을 설정하기 위해 `timedelta` 를 생성합니다.

실제 JWT 액세스 토큰을 생성하여 반환합니다.

{* ../../docs_src/security/tutorial004_an_py310.py hl[118:133] *}

### JWT "주체(subject)" `sub`에 대한 기술 세부 사항

- Upon receiving a LIST request with an expired continue token, the apiserver now returns a continue token together with the 410 "the from parameter is too old" error. If the client does not care about getting a list from a consistent snapshot, the client can use this token to continue listing from the next key, but the returned chunk will be from the latest snapshot. ([#67284](https://github.com/kubernetes/kubernetes/pull/67284),...

    // ============================================================

    /** User information session key. */
    public static final String USER_INFO = "LoginInfo";

    /** Search engine API access token key. */
    public static final String SEARCH_ENGINE_API_ACCESS_TOKEN = "searchEngineApiAccessToken";

    /** Default field name identifier. */
    public static final String DEFAULT_FIELD = "_default";

* Some components like kube-dns and kube-proxy could fail to load the service account token when started within a pod. Properly handle empty configurations to try loading the service account config. ([#31947](https://github.com/kubernetes/kubernetes/pull/31947), [@smarterclayton](https://github.com/smarterclayton))

 * kubeadm: The Token-related fields in the `MasterConfiguration` object have now been refactored. Instead of the top-level `.Token`, `.TokenTTL`, `.TokenUsages`, `.TokenGroups` fields, there is now a `BootstrapTokens` slice of `BootstrapToken` objects that support the same features under the `.Token`, `.TTL`, `.Usages`, `.Groups` fields. ([#64408](https://github.com/kubernetes/kubernetes/pull/64408), [@lu...

labels.reading=읽기
labels.roleTypeIds=역할 ID
labels.scriptData=스크립트
labels.scriptResult=결과
labels.scriptType=실행 방법
labels.segmentation=분할
labels.startTime=시작 시간
labels.target=대상
labels.token=토큰
labels.synonymFile=동의어 파일
labels.stopwordsFile=불용어 파일
labels.stemmerOverrideFile=Stemmer 덮어쓰기 파일
labels.mappingFile=매핑 파일
labels.protwordsFile=Protwords 파일
labels.kuromojiFile=Kuromoji 파일

labels.roleTypeIds=ID ролей
labels.scriptData=Скрипт
labels.scriptResult=Результат
labels.scriptType=Метод выполнения
labels.segmentation=Сегментация
labels.startTime=Время начала
labels.target=Цель
labels.token=Токен
labels.synonymFile=Файл синонимов
labels.stopwordsFile=Файл стоп-слов
labels.stemmerOverrideFile=Файл переопределения стеммера
labels.mappingFile=Файл сопоставления
labels.protwordsFile=Файл Protwords

* Bump up pod short start timeout to 2 minutes. ([#69291](https://github.com/kubernetes/kubernetes/pull/69291), [@mrunalp](https://github.com/mrunalp))
* Use the mounted "/var/run/secrets/kubernetes.io/serviceaccount/token" as the token file for running in-cluster based e2e testing. ([#69273](https://github.com/kubernetes/kubernetes/pull/69273), [@dims](https://github.com/dims))