Terminology

Description

Cluster

A set of worker machines, called nodes, that run containerized applications. Every cluster has at least one worker node.

Namespace

An abstraction used by Kubernetes to support multiple virtual clusters on the same physical cluster.

Node

A node is a worker machine in Kubernetes.

Container

A lightweight and portable executable image that contains software and all of its dependencies.

Kubernetes Object

An entity in the Kubernetes system. The Kubernetes API uses these entities to represent the state of your cluster.

Pod

The smallest and simplest Kubernetes object. A Pod represents a set of running containers on your cluster.

Charts

A chart is a packaging format used by Helm to represent a collection of files that describe a related set of Kubernetes resources. A single chart might be used to deploy a simple memcached pod, or a complex web application stack with databases, caches, and so on.

Application Group

An application group is a Kubernetes application, as defined by the application admin, that is eligible for backup.

Recipe

A Recipe is a label that defines the state of data by which the backup must be performed, as defined by the Application Admin.
Recipes are the backup definition criteria for the data state upon backup execution, for example, application-consistent, crash-consistent, and so on.

CRD (Custom Resource Definition)

Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server.

 Finalizer

Finalizers are namespaced keys that tell Kubernetes to wait until specific conditions are met before it fully deletes resources marked for deletion. Finalizers alert controllers to clean up resources the deleted object owned.

Kubectl

A command line tool for communicating with a Kubernetes API server.

Volume

A directory containing data, accessible to the containers in a Pod.

Workload

A workload is an application running on Kubernetes.