Deployments

Deployments are a mechanism for managing and scaling the pods that make up an application in Kubernetes. Deployments let you create, update, and scale Kubernetes applications. They help control rollout of a new application version and manage scaling. They also manage the application lifecycle, including automatic recovery after failures and automatic scaling based on demand.

The Deployments tab lists Deployments created in the namespace context.

Creating a Deployment #

To add a new Deployment, click + Add Deployment.

In the dialog that opens, fill in the Deployment description.

In the Deployment management block:

• set the number of replicas. Default is 1 replica;
• set the Deployment type. Default is RollingUpdate;
• set whether the Deployment is paused. Default is not set;
• for a RollingUpdate Deployment, set maximum unavailable and maximum surge. Default is 25%;
• set ProgressDeadlineSeconds — the time in seconds to wait for a rollout before it is marked failed. Default is 600 seconds (10 minutes). The controller reports that the rollout has stalled only after this period elapses;
• set RevisionHistoryLimit — the number of ReplicaSets to retain for rollback. Default is 10.

In the Pod template block, the following settings are available:

• use hostPID? Default is not selected.
• use host network? Default is not selected.
• select image pull secrets (Image Pull Secrets) from the drop-down list. The list shows secrets created on the Storage tab in the Namespace section.
• assign priority. Priority reflects the importance of the pod relative to other pods in the cluster. If a pod lacks resources to start, the scheduler prefers pods with higher priority values.
• set the container hostname.
• if needed, create Tolerations. Click + and fill in the fields in the dialog that opens.
• set nodes. Click + in the node selector. Note! Label selectors use logical AND. The selected object must have all specified labels.
• select ServiceAccountName from the drop-down list.
• define whether to mount the service account token. Default is not set.

In the Init containers and Containers blocks, the following settings are available:

• set the container name;
• enter the image value;
• set Image Pull Policy. Default is ifNotPresent;
• if needed, add commands and arguments;
• define ports. To add a new port, click +.

• set compute resources:
  • CPU request and limit values. You can set them in CPU or m (milli-CPU).
  • Memory request and limit values. You can use Kubernetes-standard units: byte (B), kibibyte (Ki), mebibyte (Mi), gibibyte (Gi).

• set volume mounts. To add a new volume mount, click +.

• set environment variables. To add a new variable, click +.

For section settings, see the Pods page.

After finishing the settings, click Add.

Viewing a Deployment #

The Deployment view page has tabs:

• Deployment
• Pod template (includes Containers, Init containers, and Volumes)
• HPA
• ReplicaSets
• Pods (shows a count)
• Security
• Labels and annotations (list of Deployment labels and annotations)
• Events (shows a count)
• Manifest

Deployment tab #

The Deployment tab shows Deployment details, creation date and time, status, and state. The Specification block includes:

• Name
• Deployment type
• Paused / Not paused

The scaling block lets you change the number of replicas.

The Monitoring metrics block shows CPU Usage and Memory Usage for all Deployment objects combined over the past hour.

The Pod selector is available. Note! Label selectors use logical AND. The selected object must have all specified labels.

Pod template tab #

Shows the pod template, containers, init containers, and volumes of the Deployment.

HPA tab #

On the HPA tab you can manage automatic scaling of Deployment pods. Set the target average count or average relative value over the last 5 minutes for:

• CPU;
• Memory.

When the value is exceeded, the number of pods increases within the configured replica range. When load decreases, the number of pods decreases. The HPA object is created with an automatically generated name. You can manage the object only from the created Deployment tab. You can view or edit the object manifest and delete a previously created HPA.

ReplicaSets tab #

Lists ReplicaSets that belong to the Deployment with details:

• when the ReplicaSet was created;
• status;
• total number of pods and number of running pods;
• ReplicaSet image details.

Click a ReplicaSet row to open the ReplicaSet view page.

Pods tab #

Lists pods owned by the Deployment with details:

• Pod name (filterable).
• Ratio of running containers to total containers in the pod.
• Pod restart count (sortable).
• Creation date (sortable).
• Namespace (filterable). Clicking the namespace name opens the namespace dashboard. Enter a value to filter pods by namespace. To clear namespace filtering, click Cancel in the filter, then Apply.
• Status (filterable). Filter values: Running, Pending, Terminating, CrashLoopBackOff, Completed, Failed, Unknown.
• Parent object (filterable). When the pod belongs to a workload, clicking the workload name opens its view page.
• Node where the pod runs (filterable). Clicking the node opens the node view page if you have access.
• Pod QoS (Quality of Service) (filterable: Guaranteed, Burstable, BestEffort). For more about QoS, see Pods.
• Pod labels (the Labels column is hidden by default). To show pod labels, click the gear icon in the table corner and enable the Labels column.

Click a pod row to open the pod view page.

Security tab #

The Security tab shows:

• image vulnerability scan results for objects in this Deployment (shown only if the Container Image Scanning module is installed in the cluster);
• policy compliance analysis results for objects in this Deployment (shown only if the Application Configuration Analysis module is installed in the cluster).

Events tab #

Lists Deployment and related object events with details:

• event type indicator;
• date and time;
• event source;
• event message text.

Manifest tab #

On the Manifest tab of the view and edit pages for an existing Deployment, you can change the YAML manifest, copy the manifest, or delete the Deployment. After changing the manifest, run validation. The validation result appears on the right side of the screen. Expand the validation result block to see the full manifest. If Deployment manifest format validation fails, manifest validation is unavailable.

Save the changes made to the manifest. Unsaved data will not be applied. If the Deployment has at least one privileged container, that information is shown on the tab.