deployments

Name: deployments
Availability: InStock
Author: theslashdojo

Manage Kubernetes Deployments to create, update, scale, and rollback stateless applications.

Updated Apr 10, 2026

Search Tags:#rollback #kubernetes #kubectl #scaling #deployments #rolling-update #replicaset

Ready to run

npx skills add https://github.com/theslashdojo/dojo --skill deployments-theslashdojo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deployments
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/kubernetes/deployments
Command: npx skills add https://github.com/theslashdojo/dojo --skill deployments-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Orchestrates the lifecycle of stateless Kubernetes applications so agents and operators can reliably create, update, scale, and rollback Deployments without manual, error-prone kubectl sequences.

Core Features & Use Cases

Declarative and Imperative Deployment: Apply manifests or create deployments imperatively and manage replicas.
Rolling Updates and Rollbacks: Perform image updates with controlled rollout parameters and revert to previous revisions when needed.
Scaling and Verification: Scale replicas, inspect rollout status and history, and surface ReplicaSet and Pod info for troubleshooting.
Use Case: Deploy a web service, perform a zero-downtime image upgrade, and rollback automatically if readiness probes fail.

Quick Start

Tell the skill to deploy web-app using image myregistry/web-app:v1.2.0 with 3 replicas to the production namespace and wait for the rollout to complete.

Frequently Asked Questions about deployments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform a rolling update on a Kubernetes deployment without downtime?▼

Kubernetes rolling updates replace old pods with new ones gradually. You control rollout parameters like maxSurge and maxUnavailable to maintain availability while updating ReplicaSets and verifying rollout status automatically.

Why does my Kubernetes rollout fail and how do I rollback to the previous version?▼

Kubernetes rollbacks revert deployments to previous revisions when readiness probes fail. You can inspect rollout history and ReplicaSet status to troubleshoot failed releases, then trigger an automatic or manual rollback to recover the working stateless application.

How do I scale Kubernetes replicas for a stateless application?▼

Scaling Kubernetes replicas adjusts pod instances for stateless applications. Update replica counts in deployment manifests or use kubectl imperatively to match workload demands and verify ReplicaSet status.

Do I need kubectl configured to manage Kubernetes deployments?▼

Yes, kubectl configured with cluster access is required to manage Kubernetes Deployments. You also need container images in a reachable registry, and can optionally specify namespaces and rollout strategy parameters like maxSurge and maxUnavailable.

What is the best way to verify Kubernetes rollout status after an image update?▼

Verifying Kubernetes rollout status involves inspecting deployment rollout progress and ReplicaSet information. Surface pod and ReplicaSet details to ensure new pods pass readiness probes and the rollout completes successfully.

Can I use declarative manifests and imperative commands for Kubernetes deployments?▼

Yes, Kubernetes Deployments support both declarative manifest application and imperative command creation. Apply manifests to define deployments and manage replicas, or create deployments imperatively and perform rolling updates and rollbacks.