Release Notes and Announcements
- Release Notes
- Announcements
- Release Notes
Product Introduction
Purchase Guide
- Purchase Instructions
- Purchase a TKE General Cluster
- Purchasing Native Nodes
- Purchasing a Super Node
Getting Started
Cluster Configuration
- General Cluster Overview
- Cluster Management
- Network Management
- Storage Management
- Node Management
- Images
- GPU Resource Management
- Remote Terminals
Application Configuration
- Workload Management
- Service and Configuration Management
- Component and Application Management
- Auto Scaling
- Container Login Methods
Observability Configuration
- Ops Observability
- Cost Insights and Optimization
Scheduler Configuration
- Scheduling Component Overview
- Resource Utilization Optimization Scheduling
- Business Priority Assurance Scheduling
- QoS Awareness Scheduling
Security and Stability
- TKE Security Group Settings
- Identity Authentication and Authorization
- Control Plane Security
- Application Security
- Cluster Security Enhancement Capability
Multi-cluster Management
- Planned Upgrade
- Backup Center
Cloud Native Service Guide
- Cloud Service for etcd
- TMP
- TKE Serverless Cluster Guide
- TKE Registered Cluster Guide
Use Cases
- Cluster
- Serverless Cluster
- Scheduling
- Security
- Service Deployment
- Network
- Release
- Logs
- Monitoring
- OPS
- Terraform
- DevOps
- Auto Scaling
- Containerization
- Cost Management
- Hybrid Cloud
- AI
Troubleshooting
API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Elastic Cluster APIs
- Resource Reserved Coupon APIs
- Cluster APIs
- Third-party Node APIs
- Relevant APIs for Addon
- Node Pool APIs
- Network APIs
- Node APIs
- Node Pool APIs
- TKE Edge Cluster APIs
- Cloud Native Monitoring APIs
- Scaling group APIs
- Super Node APIs
- Other APIs
- Data Types
- Error Codes
- TKE API 2022-05-01
FAQs
- TKE Standard Cluster
- TKE Serverless Cluster
- About OPS
- Hidden Danger Handling
- About Services
- Image Repositories
- About Remote Terminals
- Event FAQs
- Resource Management
Service Agreement
- TKE Service Level Agreement
- TKE Serverless Service Level Agreement
Contact Us
Glossary

GooseFS-CSI (Tencent Cloud GooseFS)

Baixar

Modo Foco

Tamanho da Fonte

Última atualização: 2026-10-23 15:37:53

Traduzido e Verificado por IA

Component Introduction
For component details, see GooseFS-CSI Description.
Change Records
Release Date
Version Number
Change Content
Limitations and Impact
2026-08-12
v1.0.5
PVs support heterogeneous client versions/client-side caching.
Fixed an issue where unmounting a mount point failed but returned success.
Cluster version > 1.14.
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.
2026-04-14
v1.0.4
Supports dynamically updating the mount parameters of the FUSE client in a PV, including javaOptions and mountOptions.
Cluster version > 1.14.
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.
2026-03-02
v1.0.3
Supports upgrading the fuse client edition and flexibly specifying the monitoring report address, obtains goosefsMonitorUrl from the request volume context, and injects it into the environment variable GOOSEFS_MONITOR_REPORT_URL.
Cluster version > 1.14.
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.
2025-09-11
v1.0.2
When starting the fuse-pod, inject the goosefs cluster ID and user UIN to report monitoring metrics.
When mounting a goosefs PV, wait for the fuse pod being deleted to complete its termination before starting a new fuse-pod. This prevents the mount point from becoming inaccessible after the old fuse-pod is deleted.
Add the --pv-to-keep-fuse-pod parameter to retain the fuse-pod on the node after all goosefs service pods on that node have terminated, thereby accelerating the restart speed of service pods.
When insufficient node resources prevent the fuse-pod from starting, log the event and record it to facilitate troubleshooting.
The goosefs fuse-pod image version is upgraded to v1.4.8.5.
Cluster version > 1.14.
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.
2025-03-17
v1.0.1
Fixes the issue where newly created service pods mount local directories after the goosefs fuse-pod is deleted or evicted.
Cluster version > 1.14.
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.
2025-02-28
v1.0.0
Releases the GooseFS-CSI component, supporting the use of GooseFS in CSI mode.
Cluster version > 1.14.
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.

Ajuda e Suporte

Esta página foi útil?

Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.

comentários

tencent cloud

Tencent Kubernetes Engine

GooseFS-CSI (Tencent Cloud GooseFS)

Component Introduction

Change Records

Ajuda e Suporte

Release Date	Version Number	Change Content	Limitations and Impact
2026-08-12	v1.0.5	PVs support heterogeneous client versions/client-side caching. Fixed an issue where unmounting a mount point failed but returned success.	Cluster version > 1.14. 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.
2026-04-14	v1.0.4	Supports dynamically updating the mount parameters of the FUSE client in a PV, including `javaOptions` and `mountOptions`.	Cluster version > 1.14. 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.
2026-03-02	v1.0.3	Supports upgrading the fuse client edition and flexibly specifying the monitoring report address, obtains goosefsMonitorUrl from the request volume context, and injects it into the environment variable GOOSEFS_MONITOR_REPORT_URL.	Cluster version > 1.14. 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.
2025-09-11	v1.0.2	When starting the fuse-pod, inject the goosefs cluster ID and user UIN to report monitoring metrics. When mounting a goosefs PV, wait for the fuse pod being deleted to complete its termination before starting a new fuse-pod. This prevents the mount point from becoming inaccessible after the old fuse-pod is deleted. Add the --pv-to-keep-fuse-pod parameter to retain the fuse-pod on the node after all goosefs service pods on that node have terminated, thereby accelerating the restart speed of service pods. When insufficient node resources prevent the fuse-pod from starting, log the event and record it to facilitate troubleshooting. The goosefs fuse-pod image version is upgraded to v1.4.8.5.	Cluster version > 1.14. 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.
2025-03-17	v1.0.1	Fixes the issue where newly created service pods mount local directories after the goosefs fuse-pod is deleted or evicted.	Cluster version > 1.14. 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.
2025-02-28	v1.0.0	Releases the GooseFS-CSI component, supporting the use of GooseFS in CSI mode.	Cluster version > 1.14. 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.