tencent cloud

Tencent Kubernetes Engine

Release Notes and Announcements
Release Notes
Announcements
Release Notes
Product Introduction
Overview
Strengths
Architecture
Scenarios
Features
Concepts
Native Kubernetes Terms
Common High-Risk Operations
Regions and Availability Zones
Service Regions and Service Providers
Open Source Components
Purchase Guide
Purchase Instructions
Purchase a TKE General Cluster
Purchasing Native Nodes
Purchasing a Super Node
Getting Started
Beginner’s Guide
Quickly Creating a Standard Cluster
Examples
Container Application Deployment Check List
Cluster Configuration
General Cluster Overview
Cluster Management
Network Management
Storage Management
Node Management
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
Application Security
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
Microservice
Cost Management
Hybrid Cloud
AI
Troubleshooting
Disk Full
High Workload
Memory Fragmentation
Cluster DNS Troubleshooting
Cluster kube-proxy Troubleshooting
Cluster API Server Inaccessibility Troubleshooting
Service and Ingress Inaccessibility Troubleshooting
Common Service & Ingress Errors and Solutions
Engel Ingres appears in Connechtin Reverside
CLB Ingress Creation Error
Troubleshooting for Pod Network Inaccessibility
Pod Status Exception and Handling
Authorizing Tencent Cloud OPS Team for Troubleshooting
CLB Loopback
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
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 General 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

COS-CSI

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2024-02-01 10:03:01

Overview

Add-on description

The Kubernetes-csi-tencentcloud COS-CSI plug-in allows you to use Tencent Cloud Object Storage (COS) in your TKE cluster.

Kubernetes objects deployed in a cluster

Kubernetes Object Name
Type
Default Resource Consumption
Namespaces
csi-coslauncher
DaemonSet
-
kube-system
csi-cosplugin
DaemonSet
-
kube-system
csi-cos-tencentcloud-token
Secret
-
kube-system

Use Cases

COS is a distributed storage service provided by Tencent Cloud to store massive files. You can store and view data at any time over a network. Tencent Cloud COS provides scalable, affordable, reliable, and secure data storage services for all users.
With the COS-CSI add-on, you can quickly use COS as COSFS in your cluster through standard native Kubernetes. For more information, see COSFS.

Limits

Supports clusters with Kubernetes version 1.10 and later.
For Kubernetes 1.12 clusters, the following kubelet configuration must be added: --feature-gates=KubeletPluginsWatcher=false.
For more information on the limits of COSFS, see COSFS.
To use COS in TKE, you must install this add-on in your cluster, which consumes some system resources.

COS-CSI Permission

Permission Description

The permission of this component is the minimal dependency required for the current feature to operate.
The related directory /var/lib/kubelet on the host machine needs to be mounted to the container to accomplish volume mount/unmount, hence the activation of the privileged-level container is required.

Permission Scenarios

Feature
Involved Object
Involved Operation Permission
Supporting COS bucket mounting in lite mode
PersistentVolume
get/watch/list/update
pod
get/create/delete/update
Storing related COS configuration in the lite mounting method
configmap
get/create/delete/update

Permission Definition

kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: csi-cos-tencentcloud
rules:
- apiGroups: [""]
resources: ["events", "persistentvolumes"]
verbs: ["get", "watch", "update", "list"]
- apiGroups: [""]
resources: ["pods", "configmaps"]
verbs: ["get", "create", "delete", "update"]

Usage

Installing the COS add-on

1. Log in to the TKE console and select Cluster in the left sidebar.
2. On the "Cluster Management" page, click the ID of the target cluster to go to the cluster details page.
3. In the left sidebar, click Add-On Management to go to the "Add-On List" page.
4. On the "Add-On List" page, click Create. On the "Create an Add-On" page that appears, select COS.
5. Click Finish to create the add-on.

Using COS

You can mount COS for workloads in a TKE cluster. For more information, see Using COS.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan