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=提升词文件

testdata/huffman-zero.wb.expect", "src/compress/flate/testdata/huffman-zero.wb.expect-noinput", "src/compress/flate/testdata/null-long-match.dyn.expect-noinput", "src/compress/flate/testdata/null-long-match.wb.expect-noinput", "src/compress/flate/token.go", "src/compress/flate/writer_test.go", "src/compress/gzip/", "src/compress/gzip/example_test.go", "src/compress/gzip/gunzip.go", "src/compress/gzip/gunzip_test.go", "src/compress/gzip/gzip.go", "src/compress/gzip/gzip_test.go", "src/compress/gz...

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 파일

- Kube-apiserver can now specify `--authentication-token-webhook-version=v1` or `--authorization-webhook-version=v1` to use `v1` TokenReview and SubjectAccessReview API objects when communicating with authentication and authorization webhooks. ([#84768](https://github.com/kubernetes/kubernetes/pull/84768), [@liggitt](https://github.com/liggitt))

For most migration scenarios, we recommend using the modern JSON Search API (`/api/v1/documents`) instead.

### Admin APIs

All admin APIs require authentication (`-u admin:admin` or Bearer token).

**Base Path**: `/api/admin/`

**Available Endpoints**:
- `POST /backup/upload` - Upload backup/import files
- `GET /backup/export` - Export configurations
- `PUT /documents/bulk` - Bulk document import

### VMware

- SAML token delegation (required for Zones support in vSphere) is now supported ([#78876](https://github.com/kubernetes/kubernetes/pull/78876), [@dougm](https://github.com/dougm))
- vSphere SAML token auth is now supported when using Zones ([#75515](https://github.com/kubernetes/kubernetes/pull/75515), [@dougm](https://github.com/dougm))

			if value := env.Get(config.EnvMinIOPrometheusExtraLabels, ""); value != "" {
				os.Setenv("CONSOLE_PROMETHEUS_EXTRA_LABELS", value)
			}
		}
		// Support Prometheus Auth Token
		if value := env.Get(config.EnvMinIOPrometheusAuthToken, ""); value != "" {
			os.Setenv("CONSOLE_PROMETHEUS_AUTH_TOKEN", value)
		}
	}
	// Enable if LDAP is enabled.
	if globalIAMSys.LDAPConfig.Enabled() {

### **Cluster Lifecycle**

*   You must either specify the `--discovery-token-ca-cert-hash` flag to `kubeadm join`, or opt out of the CA pinning feature using `--discovery-token-unsafe-skip-ca-verification`.
*   The default `auto-detect` behavior of the kubelet's `--cloud-provider` flag is removed.

ServiceAccount. Use the [TokenRequest](https://kubernetes.io/docs/reference/kubernetes-api/authentication-resources/token-request-v1/) API to acquire service account tokens, or if a non-expiring token is required, create a Secret API object for the token controller to populate with a service account token by following this [guide](https://kubernetes.io/docs/concepts/configuration/secret/#service-account-token-secrets). ([#108309](https://github.com/kubernetes/kubernetes/pull/108309), [@zshihang](https://github.com/zshihang))...

* `--service-account-lookup` now defaults to true, requiring the Secret API object containing the token to exist in order for a service account token to be valid. This enables service account tokens to be revoked by deleting the Secret object containing the token. ([#44071](https://github.com/kubernetes/kubernetes/pull/44071), [@liggitt](https://github.com/liggitt))