Instructions for Beginners
This document provides instructions for getting started with the Cloud Container Engine (CCE).
Complete the following tasks to get started with CCE.
- Authorize an IAM user to use CCE.
HUAWEI CLOUD accounts have the permission to use CCE. However, IAM users created by HUAWEI CLOUD accounts do not have the permission. You need to manually assign the permission to IAM users. For details, see Permissions Management by IAM.
- Create a cluster.
- Create a workload from images or a chart.
Select existing images/chart, or create new images/chart.
- View workload status and logs. Upgrade, scale, and monitor the workload.
For details, see Basic Deployment Operations.
- 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 Enterprise Applications in the Help Center. You can also follow the ContainerOps User Guide or Building a Docker Image section in the Software Repository for Container (SWR) User Guide.
- Is CCE suitable for users who have little experience in building images?
Yes. You can select images from Official Docker Hub 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 Images.
- 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 Images.
- How do I create a workload accessible to public networks?
CCE provides different workload access types to address diverse scenarios. Currently, CCE provides three access types to expose a workload to public networks: NodePort, LoadBalancer, and DNAT gateway. For details, see Setting Workload Access.
- 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 an intra-cluster access (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>.