Term | English | Description |
application service | Application service | This concept is consistent with classic application services. However, because containers have unique properties, an application service in AKS includes extra metadata, such as container specifications, images, scheduling policies, and log configurations. |
image | Image | An image is a binary package for an application. It bundles the configuration and related software. The image must comply with the Docker Image specification. Images can be pulled from any image center accessible by the AKS network. For private image centers, configure the access information in AKS. |
build | Build | A build defines the configuration for creating an image from source code. This configuration includes the source code address, branch information, source image access details, target image information, and the Dockerfile location. |
cluster | Cluster | In AKS, a cluster describes a workload cluster that you create. It consists of multiple nodes. |
node | Node | A node is a physical or virtual machine with Docker and Kubelet installed to run application workloads. |
pod | Pod | A pod is the smallest deployable and manageable unit in Kubernetes. A pod consists of one or more related containers that share storage. |
namespace | Namespace | A namespace is the same as in Kubernetes. It provides a logically isolated space for resources such as pods, services, and ReplicaSets. Network traffic is typically not isolated between namespaces. |
in-place upgrade | In-place upgrade | An in-place upgrade is a method for updating pods in an application service. With this method, the pod's IP address does not change after the update. The pod also remains on the same node if possible. |
native deployment | Cloud-native deployment | A cloud-native deployment is another method for updating pods in an application service. With this method, the pod's IP address usually changes after the update. The node where the pod runs might also change. |
label | Label | A label is a native Kubernetes concept. Labels are attached to resources to organize them or to select subsets of them. |
taint | Taint | A taint is a native Kubernetes concept. Taints are applied to nodes and are used with pod scheduling policies. The corresponding concept for a pod is a toleration. If a pod has a toleration that matches a node's taint, it can be scheduled to that node. |
secret | Secret | A secret is a native Kubernetes concept. It is used to store a user's encrypted content. |
application container | Container | A container is an isolated workspace where an application runs. It is typically a Docker container or another sandbox environment, such as Pouch, that is compatible with the Container Runtime Interface (CRI) and provides isolation. |
workload | Workload | A workload refers to the running state of an application and its higher-level aggregations. Common workloads include pods, deployments, StatefulSets, DaemonSets, and Jobs. |
configuration item | ConfigMap | A ConfigMap is a native Kubernetes concept used to store user configuration data. |
Storage class | StorageClass | A StorageClass is a native Kubernetes concept, usually defined by a system administrator. It specifies the supported types of storage. Different types can have different Service-Level Agreements (SLAs), backup policies, and other characteristics. |
persistent volume (PV) | Persistent Volume | A persistent volume (PV) is a native Kubernetes concept. It represents a piece of storage in the cluster that has been provisioned by an administrator. |
persistent volume claim (PVC) | Persistent Volume Claim (PVC) | A persistent volume claim (PVC) is a native Kubernetes concept. A PVC binds to a persistent volume. |