This section describes how to use Cloud Container Engine (CCE) and provides frequently asked questions (FAQs) to help you quickly get started with CCE.
You can use CCE by using the console, kubectl (Kubernetes command-line tool), and application programming interfaces (APIs). For details about CCE concepts, see Basic Concepts.
Complete the following tasks to get started with CCE.
- Register a HUAWEI CLOUD account and grant permissions to IAM users.
HUAWEI CLOUD accounts have the permissions to use CCE. However, IAM users created by a HUAWEI CLOUD account do not have the permission. You need to manually grant the permission to IAM users. For details, see Permissions Management.
- Create a cluster.
For details on how to create a regular Kubernetes cluster, see Creating a CCE Cluster.
- Create a workload from an image or chart.
- View workload status and logs. Upgrade, scale, and monitor the workload.
For details, see Managing Workloads and Jobs.
- Is HUAWEI CLOUD CCE suitable for users who are not familiar with Kubernetes?
Yes. The CCE console is easy-to-use, and the Getting Started guide helps you quickly understand and use CCE.
- Where can I find the instructions on creating Docker images for traditional applications?
For details, see Containerizing an Enterprise Application (ERP) in the CCE Best Practices.
- Is CCE suitable for users who have little experience in building images?
Yes. You can select images from Open Source Images, Third-party Images, and Shared Images pages on the CCE console. The My Images page displays only the images created by you. For details, see Creating a Deployment (Nginx) from an Image.
- How do I create a workload using CCE?
Create a cluster and then create a workload in the cluster. For details, see Creating a Deployment (Nginx) from an Image.
- How do I create a workload accessible to public networks?
CCE provides different workload access types to address diverse scenarios. For details, see Networking Overview.
- How can I allow multiple workloads in the same cluster to access each other?
Select the access type ClusterIP, which allows workloads in the same cluster to use their cluster-internal domain names to access each other.
Cluster-internal domain names are in the format of <self-defined service name>.<workload's namespace>.svc.cluster.local:<port number>. For example, nginx.default.svc.cluster.local:80.
Assume that workload A needs to access workload B in the same cluster. Then, you can create a ClusterIP Service for workload B. After the ClusterIP Service is created, workload B is reachable at <self-defined service name>.<workload B's namespace>.svc.cluster.local:<port number>.
Was this page helpful?Provide feedback
For any further questions, feel free to contact us through the chatbot.Chatbot