お知らせ・リリースノート
- 製品アップデート情報
- 製品リリース記録
製品の説明
クイックスタート
- 初心者ガイド
- 標準クラスターのクイック作成
- ビギナー向け事例
- コンテナアプリケーションのクラウドへのデプロイ Check List
TKE標準クラスターガイド
- テンセントクバネティスエンジン
- クラスター管理
- ネットワーク管理
- ストレージ管理
- Worker ノードの概要
Kubernetes Object Management
- ワークロード
クラウドネイティブサービスガイド
- Prometheus監視サービス
- TKE Serverlessクラスターガイド
- TKE登録クラスターガイド
実践チュートリアル
- Serverlessクラスター
- ネットワーク
- ログ
- 監視
- 運用・保守
- DevOps
- オートスケーリング
よくあるご質問
- クラスター類
- TKE Serverlessクラスター
- 運用保守系
- サービス類
- イメージリポジトリ類
- リモート端末類

COS-CSI (Tencent Cloud Object Storage Component)

ダウンロード

フォーカスモード

フォントサイズ

最終更新日: 2026-10-23 15:27:43

AI翻訳

Component Introduction
For component details, see the COS-CSI description.
Must-Knows
If you install both COS-CSI v1.0.5 or later and CFS-CSI v1.1.6 or earlier, a port conflict occurs because the DaemonSets in both components have hostNetwork enabled and their metrics services use port 9097 by default. Consequently, a Pod from one of the DaemonSets fails to bind, and the following error message is logged: Failed to listen on :9097: listen tcp :9097: bind: address already in use.
This issue prevents the component from providing metrics services, but it does not affect the component's primary features.
To resolve this issue, modify the CFS-CSI component daemonset -n kube-system csi-nodeplugin-cfsplugin by adding the parameter --metric_port=9096 to the cfs container. This explicitly sets the metrics service port to 9096 (which is also the default port for CFS-CSI v1.1.7+), thereby avoiding a port conflict with COS-CSI.
Change Records
Release Date
Version Number
Change Content
Limitations and Impact
2026-08-26
v1.0.13
Supports dynamic awareness of the kubelet root-dir directory, resolving the issue of inconsistent kubelet root-dir configurations across different nodes.
Cluster version > 1.18.
When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading.
When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2026-03-24
v1.0.12
The csi-cosplugin daemonset cosfs container supports setting the cluster region via the --region parameter (for example, --region=ap-guangzhou), eliminating the need to rely on Tencent Cloud internal services to obtain region information.
Cluster version > 1.18.
When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading.
When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2025-06-26
v1.0.11
The cosfs tool is updated to version 1.0.23. When the cos PV mount option includes -oenable_clientinfo, deleting a cos file records the pod and container id information of the request initiator for traceability.
Cluster version > 1.18.
When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading.
When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2025-01-08
v1.0.8
During an upgrade, retain the manually set OnDelete update policy for the daemonset csi-coslauncher and csi-cosplugin to prevent rolling updates from affecting existing cosfs services hosted as Pods.
Cluster version > 1.18.
When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading.
When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2024-12-17
v1.0.7
Fixed the issue introduced in version 1.0.5 where a zombie process would be generated when a service Pod exited while cosfs was hosted as a Pod.
Cluster version > 1.18.
When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading.
When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2024-09-26
v1.0.6
The coredump setting for cos launcher is disabled by default. It can be enabled by setting the environment variable ENABLE_COREDUMP=true.
Cluster version > 1.18.
When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading.
When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2024-05-14
v1.0.5
cos-csi adds a health status metric for mounted targets.
The cosfs mount operation can be managed on cvm.
Cluster version > 1.18.
When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the DaemonSet csi-coslauncher and csi-cosplugin to OnDelete before component upgrades are performed. Migrate cosfs services node by node before the upgrade is performed.
When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2023-11-30
v1.0.4
The cos-csi plugin restricts some permissions to enhance component security.
When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the Daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading.
When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2023-09-21
v1.0.3
Optimizations:
During cosfs mounting, the odbglevel and opasswd_file parameters follow the user's configuration.
The umount operation supports reentrancy to prevent a pod from remaining in the terminating state after its mount directory is deleted.
Upgrade the cosfs version to improve stability.
Configure core dump for cosfs to enable troubleshooting after the cosfs process crashes.
New feature:
Adds cos and hot-mounts it using the goose-lite method.
Enable full tolerance for the cos component.
When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading.
When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2022-05-06
v1.0.1
The plugin supports configuring taint toleration.
This upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.

ヘルプとサポート

この記事はお役に立ちましたか？

営業担当者にお問い合わせいただくかチケットを提出してサポートを求めることができます。

フィードバック

tencent cloud

Tencent Kubernetes Engine

COS-CSI (Tencent Cloud Object Storage Component)

Component Introduction

Must-Knows

Change Records

ヘルプとサポート

Release Date	Version Number	Change Content	Limitations and Impact
2026-08-26	v1.0.13	Supports dynamic awareness of the kubelet root-dir directory, resolving the issue of inconsistent kubelet root-dir configurations across different nodes.	Cluster version > 1.18. When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading. When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2026-03-24	v1.0.12	The csi-cosplugin daemonset cosfs container supports setting the cluster region via the `--region` parameter (for example, `--region=ap-guangzhou`), eliminating the need to rely on Tencent Cloud internal services to obtain region information.	Cluster version > 1.18. When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading. When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2025-06-26	v1.0.11	The cosfs tool is updated to version 1.0.23. When the cos PV mount option includes `-oenable_clientinfo`, deleting a cos file records the pod and container id information of the request initiator for traceability.	Cluster version > 1.18. When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading. When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2025-01-08	v1.0.8	During an upgrade, retain the manually set OnDelete update policy for the daemonset csi-coslauncher and csi-cosplugin to prevent rolling updates from affecting existing cosfs services hosted as Pods.	Cluster version > 1.18. When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading. When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2024-12-17	v1.0.7	Fixed the issue introduced in version 1.0.5 where a zombie process would be generated when a service Pod exited while cosfs was hosted as a Pod.	Cluster version > 1.18. When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading. When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2024-09-26	v1.0.6	The coredump setting for cos launcher is disabled by default. It can be enabled by setting the environment variable ENABLE_COREDUMP=true.	Cluster version > 1.18. When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading. When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2024-05-14	v1.0.5	cos-csi adds a health status metric for mounted targets. The cosfs mount operation can be managed on cvm.	Cluster version > 1.18. When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the DaemonSet csi-coslauncher and csi-cosplugin to OnDelete before component upgrades are performed. Migrate cosfs services node by node before the upgrade is performed. When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2023-11-30	v1.0.4	The cos-csi plugin restricts some permissions to enhance component security.	When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the Daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading. When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2023-09-21	v1.0.3	Optimizations: During cosfs mounting, the odbglevel and opasswd_file parameters follow the user's configuration. The umount operation supports reentrancy to prevent a pod from remaining in the terminating state after its mount directory is deleted. Upgrade the cosfs version to improve stability. Configure core dump for cosfs to enable troubleshooting after the cosfs process crashes. New feature: Adds cos and hot-mounts it using the goose-lite method. Enable full tolerance for the cos component.	When the cosfs hosting method is Pod, the upgrade will affect existing services that use the cosfs mounting method. Modify the update policy of the daemonset csi-coslauncher and csi-cosplugin to OnDelete before performing component upgrades. Migrate cosfs services node by node before upgrading. When the hosting method is CVM or the goosefs-lite mounting method is used, the upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.
2022-05-06	v1.0.1	The plugin supports configuring taint toleration.	This upgrade does not affect existing services. During the upgrade process, the component may be unavailable. It is recommended to upgrade during off-peak hours.