Cloud Container Engine (CCE) is a highly reliable and high-performance service that allows enterprises to manage containerized applications. With support for Kubernetes-native applications and tools, CCE makes it simple to set up an environment for running containers in the cloud.
Compatible with Kubernetes and Docker, CCE allows you to quickly create and manage containerized applications. CCE also provides enhanced interconnection capabilities, including interconnection with Elastic Load Balancing (ELB) and the cloud storage services: Elastic Volume Service (EVS) and Scalable File Service (SFS).
Before you use CCE, it is important that you have a basic understanding of what Docker is and how to use Docker commands. For more information about Docker, visit https://docs.docker.com/.
The following sections dive into basic CCE concepts in more detail.
Kubernetes coordinates a highly available cluster of cloud resources, such as nodes and virtual private clouds (VPCs), required for running containers.
Stateless application instances are independent from each other and provide the same functions. They support auto scaling and rolling upgrades. Examples of stateless applications include Nginx and WordPress.
Stateful application instances are dependent on each other and have stable persistent storage and network identifiers. They support ordered deployment, scaling in, and deletion. Examples of stateful applications include MySQL High Availability (HA) and etcd applications.
A job is a resource object that Kubernetes uses to control tasks in batches. A job creates one or more pods and ensures that a specified number of them successfully terminate. There are three main types of job: non-parallel jobs that create only one pod, parallel jobs with a fixed completion count, and parallel jobs with a work queue.
A cron job runs periodically at a specified time. A cron job object is like one line of a Linux cron table file. Cron jobs are useful for creating periodic and recurring tasks, like running backups or sending emails.
Namespaces enable division of cluster resources and objects among multiple users. Typically, namespaces are best suited for scenarios where a large number of users work across multiple projects. Multiple namespaces can be created in a single cluster with the data isolated from each other. This enables namespaces to share the services of the same cluster without affecting each other.
For example, you can deploy applications in a development environment in one namespace, and deploy applications in a test environment in another namespace.
A container image is a read-only template used to create containers. For example, a container image could contain a complete Ubuntu operating system with required programs and their dependency files installed.
Docker provides a simple way to build new container images or update existing container images. In addition to building container images on your own, you can download container images that other users have created.