El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
-
Developer Guide
- Overview
- Using Native kubectl (Recommended)
- Namespace and Network
- Pod
- Label
- Deployment
- EIPPool
- EIP
- Pod Resource Monitoring Metric
- Collecting Pod Logs
- Managing Network Access Through Service and Ingress
- Using PersistentVolumeClaim to Apply for Persistent Storage
- ConfigMap and Secret
- Creating a Workload Using Job and Cron Job
- YAML Syntax
-
API Reference
- Before You Start
- Calling APIs
- Getting Started
- Proprietary APIs
-
Kubernetes APIs
- ConfigMap
- Pod
- StorageClass
- Service
-
Deployment
- Querying All Deployments
- Deleting All Deployments in a Namespace
- Querying Deployments in a Namespace
- Creating a Deployment
- Deleting a Deployment
- Querying a Deployment
- Updating a Deployment
- Replacing a Deployment
- Querying the Scaling Operation of a Specified Deployment
- Updating the Scaling Operation of a Specified Deployment
- Replacing the Scaling Operation of a Specified Deployment
- Querying the Status of a Deployment
- Ingress
- OpenAPIv2
- VolcanoJob
- Namespace
- ClusterRole
- Secret
- Endpoint
- ResourceQuota
- CronJob
-
API groups
- Querying API Versions
- Querying All APIs of v1
- Querying an APIGroupList
- Querying APIGroup (/apis/apps)
- Querying APIs of apps/v1
- Querying an APIGroup (/apis/batch)
- Querying an APIGroup (/apis/batch.volcano.sh)
- Querying All APIs of batch.volcano.sh/v1alpha1
- Querying All APIs of batch/v1
- Querying All APIs of batch/v1beta1
- Querying an APIGroup (/apis/crd.yangtse.cni)
- Querying All APIs of crd.yangtse.cni/v1
- Querying an APIGroup (/apis/extensions)
- Querying All APIs of extensions/v1beta1
- Querying an APIGroup (/apis/metrics.k8s.io)
- Querying All APIs of metrics.k8s.io/v1beta1
- Querying an APIGroup (/apis/networking.cci.io)
- Querying All APIs of networking.cci.io/v1beta1
- Querying an APIGroup (/apis/rbac.authorization.k8s.io)
- Querying All APIs of rbac.authorization.k8s.io/v1
- Event
- PersistentVolumeClaim
- RoleBinding
- StatefulSet
- Job
- ReplicaSet
- Data Structure
- Permissions Policies and Supported Actions
- Appendix
- Out-of-Date APIs
- Change History
-
FAQs
- Product Consulting
-
Basic Concept FAQs
- What Is CCI?
- What Are the Differences Between Cloud Container Instance and Cloud Container Engine?
- What Is an Environment Variable?
- What Is a Service?
- What Is Mcore?
- What Are the Relationships Between Images, Containers, and Workloads?
- What Are Kata Containers?
- Can kubectl Be Used to Manage Container Instances?
- What Are Core-Hours in CCI Resource Packages?
- Workload Abnormalities
-
Container Workload FAQs
- Why Service Performance Does Not Meet the Expectation?
- How Do I Set the Quantity of Instances (Pods)?
- How Do I Check My Resource Quotas?
- How Do I Set Probes for a Workload?
- How Do I Configure an Auto Scaling Policy?
- What Do I Do If the Workload Created from the sample Image Fails to Run?
- How Do I View Pods After I Call the API to Delete a Deployment?
- Why an Error Is Reported When a GPU-Related Operation Is Performed on the Container Entered by Using exec?
- Can I Start a Container in Privileged Mode When Running the systemctl Command in a Container in a CCI Cluster?
- Why Does the Intel oneAPI Toolkit Fail to Run VASP Tasks Occasionally?
- Why Are Pods Evicted?
- Why Is the Workload Web-Terminal Not Displayed on the Console?
- Why Are Fees Continuously Deducted After I Delete a Workload?
-
Image Repository FAQs
- Can I Export Public Images?
- How Do I Create a Container Image?
- How Do I Upload Images?
- Does CCI Provide Base Container Images for Download?
- Does CCI Administrator Have the Permission to Upload Image Packages?
- What Permissions Are Required for Uploading Image Packages for CCI?
- What Do I Do If Authentication Is Required During Image Push?
-
Network Management FAQs
- How Do I View the VPC CIDR Block?
- Does CCI Support Load Balancing?
- How Do I Configure the DNS Service on CCI?
- Does CCI Support InfiniBand (IB) Networks?
- How Do I Access a Container from a Public Network?
- How Do I Access a Public Network from a Container?
- What Do I Do If Access to a Workload from a Public Network Fails?
- What Do I Do If Error 504 Is Reported When I Access a Workload?
- What Do I Do If the Connection Timed Out?
- Storage Management FAQs
- Log Collection
- Account
- SDK Reference
- Videos
- General Reference
Copied.
Overview
What Is CCI?
Cloud Container Instance (CCI) is a serverless container engine that allows you to run containers without creating or managing clusters.
Traditionally, to run containerized workloads using Kubernetes, you need to create a Kubernetes server cluster first. In the serverless model, a cloud provider runs servers and dynamically allocates resources so that you can build and run applications without having to worry about server statuses. This model helps you improve development efficiency and reduce IT costs.
CCI uses the serverless model that allows you to directly create and use containerized workloads on the console or by calling kubectl or Kubernetes APIs, and pay only for the resources consumed by these workloads.
![](https://support.huaweicloud.com/intl/en-us/productdesc-cci/en-us_image_0202441473.png)
Functions
One-stop Container Lifecycle Management
CCI allows you to run containers without creating or managing server clusters. With the serverless model, you can deploy and run workloads on the console or by using kubectl or Kubernetes APIs, and pay only for the resources consumed by these workloads.
Heterogeneous Network Access
Various network access modes and load balancing at both Layer 4 and Layer 7 are available to meet scenario-specific needs.
Choices of Persistent Storage Volumes
Data can be stored in Elastic Volume Service (EVS) and SFS Turbo.
Fast Auto Scaling
Scaling policies can be user-defined to implement elastic scaling within 1 second. In addition, these policies can be combined flexibly to cope with traffic surge during peak hours.
Comprehensive Container Status Monitoring
The resources consumed by containers are monitored, such as the CPU usage, memory usage, GPU compute usage, and GPU memory usage, from which you can determine the running status of the containers in real time.
Architecture
CCI integrates heterogeneous Kubernetes clusters and network and storage services, enabling you to easily create and use containerized workloads using the console, kubectl, or Kubernetes APIs.
![Click to enlarge](https://support.huaweicloud.com/intl/en-us/productdesc-cci/en-us_image_0000001726489013.png)
- CCI is deeply integrated with network services, for example Virtual Private Cloud (VPC), Elastic Load Balancer (ELB), and NAT Gateway, as well as storage services such as Elastic Volume Service (EVS).
- CCI supports high-performance and heterogeneous computing architectures such as x86, GPU, and Ascend so that containers directly run on physical servers.
- CCI uses secure containers and in-house hardware virtualization acceleration technologies for VM-level isolation, thereby providing high-performance and secure container services.
- With unified cluster management and workload scheduling, you do not need to manage clusters.
- The Kubernetes-based workload model provides fast workload deployment, elastic load balancing, auto scaling, and blue-green release.
CCI Learning Path
You can learn more about CCI so that you can use CCI and perform O&M with ease.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot